Project

General

Profile

Actions

Bug #4841

closed

Package Foreman in its own SCL

Added by Dominic Cleal about 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
RPMs
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

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:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Developer_Toolset/2/html-single/Software_Collections_Guide/index.html#sect-The_Software_Collections_Prefix
https://access.redhat.com/site/documentation/en-US/Red_Hat_Developer_Toolset/2/html-single/Software_Collections_Guide/index.html#chap-Extending_Red_Hat_Software_Collections


Related issues 4 (0 open4 closed)

Related to Installer - Bug #8371: foreman-installer tries to install foreman-release-scl on Ubuntu after upgrade from 1.6.2 to 1.7rc1Resolved11/12/2014Actions
Related to Foreman - Bug #13803: Foreman-debug does not report SCL correctlyClosedDominic Cleal02/19/2016Actions
Blocks Packaging - Feature #7228: Rebuild packages under ror41/ruby22 SCLsClosedDominic Cleal08/22/2014Actions
Blocked by Packaging - Refactor #7234: SCL 1.1 builds needed for EL rebuilds (CentOS, SL)ClosedDominic Cleal08/22/2014Actions
Actions

Also available in: Atom PDF