Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

/etc/rpm/macros.scl (which should be /usr/lib/rpm/macros.d/macros.scl) defines default values for %scl_vendor.

All other macros are compute from this value (%_scl_prefix, ...)

It's ok to inherit those values from scl-utils when building the meta-package.

But if changed in the metapackage, values should be the same for all packages in the collection, so should be inherited from the metapackage , so defined in the foo-build, in /etc/rpm/macros.foo-config (or /usr/lib/rpm/macros.d/macros.foo-config)

Use case:
- new collection php56 in BAR repository => will probably use /opt/bar
- existing php55 in RHSCL => use /opt/rh

An extension package should be able to build against php55 or php56 and provides the library in the correct tree, so %_scl_prefix have to inherit the correct value.

I'm sorry but from your description I have no idea what are you actually requesting, could you be more specific? At this point nothing prevents you from adding the scl_vendor definition in the macros.<scl>.config file.

I believe I have finally got to the bottom of this request. It's a duplicate of bug 1084095. I am closing this bug but I will keep the Fedora bug for tracking purposes. This might be a nice feature for SCL 2.0.

*** This bug has been marked as a duplicate of bug 1084095 ***