• Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • rhel-8.9.0, rhel-9.4
    • None
    • None
    • Remove upstream spec files
    • Hide

      The following needs to be verified in order for this epic to be considered complete:

       

      • Upstream stalld, tuna, python-linux-procfs and rteval have no upstream spec files
      • stalld, tuna, python-linux-procfs and rteval built in rhel-8.9.0 and rhel-9.4.0
      Show
      The following needs to be verified in order for this epic to be considered complete:   Upstream stalld, tuna, python-linux-procfs and rteval have no upstream spec files stalld, tuna, python-linux-procfs and rteval built in rhel-8.9.0 and rhel-9.4.0
    • False
    • Hide

      None

      Show
      None

      Remove upstream spec files

      spec files are maintained in rpms for example in dist-git, but there is no need to maintain them in upstream source code. In fact they tend to not be updated and confusing.
       However, there is usually some functionality related to them, for example the version number of the software is often maintained there. Some functionality related to created rpms may exist there. In the case of version numbers, they can be done else where in the software. In the case of rpms, usually the modern rpm tools such as rpmbuild and friends and also rhpkg and centpkg provide us everything we need, in which case this functionality can simply be removed from Makefiles that use the upstream specfiles.

       

      What SSTs and Layered Product teams should review this?

            jkacur@redhat.com John Kacur
            jkacur@redhat.com John Kacur
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: