Determine if adding the OS qualifier to the RPMs would be beneficial

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

StatusNOT STARTED
Impact

LOW

DriverTrevor Vaughan 
Approver
ContributorsChris Tessmer Dylan Cochran (Unlicensed) Brandon Riden (Unlicensed) Kendall Moore Liz Nemsick Judith Johnson Shark Bruhaha Michael Morrone Jeanne Greulich 
Informed
Due date
Outcome

Background

Traditionally, the SIMP RPMs were packaged where the %{dist} tag was omitted if the package had nothing that bound it to the release and included if there were distribution specific items in the RPM spec file.

Over time, this has shown to cause some difficulties around release time in that you may end up with the same package built and released twice for EL6 and EL7 when it should not have been. When you then go to point at an upstream repo, you will get YUM issues where it finds that the upstream package.

Relevant data

RHEL and its derivatives have gone to just rolling in the %{dist} tag no matter what to make everything easy to maintain. 

Options considered


Option 1:Option 2:
DescriptionLeave things the way they areAdd the %{dist} tag to all RPMs
Pros and cons

(plus) Fewer builds (only one instead of two or more)

(plus) Already done

(minus) If we don't get it 100% correct all the time, we run the risk of having the same RPM with different checksums in the associated yum repos and/or ISOs. 

(plus) There is no question what something is built for

(plus) Easy to validate that you've gotten it right both visually and automatically.

(plus) Able to release different OS versions independently without worry.

(minus) Have to roll an additional RPM for each platform (this is already automated)

Estimated costTRIVIALLOW

Action items

  •  

Outcome