Package Foreman in its own SCL
We really shouldn't be building packages inside the 'ruby193' software collection, but instead should have our own software collection (say, 'foreman') which depends upon ruby193.
Generally the provided SCLs aren't intended to have packages added to, or we could cause conflicts (e.g. ruby193-passenger is in RHSCL 1.1 but not 1.0, yet we provide it) and it will make it much harder for us to migrate to new SCLs (e.g. ruby200 and ror40) as all of our package names change.
Some docs on this are here:
#3 Updated by Dominic Cleal over 6 years ago
Started work on this in https://github.com/domcleal/foreman-packaging/tree/rpm/develop-fmrb modelled on ror40 (which is built on ruby200), but it'll depend on RHSCL 1.1 to work for the ruby193-scldevel package
#4 Updated by Dominic Cleal over 6 years ago
PR up for example purposes: https://github.com/theforeman/foreman-packaging/pull/249
#12 Updated by Dominic Cleal over 5 years ago
- Category set to RPMs
- Status changed from Ready For Testing to Closed
- Assignee set to Dominic Cleal
- % Done changed from 0 to 100
- Legacy Backlogs Release (now unused) set to 63
PR merged, packages are rebuilding. Status on the bottom of the PR and on foreman-dev.