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.

+++ This bug was initially created as a clone of Bug #1029515 +++

+++ This bug was initially created as a clone of Bug #1011360 +++

In %install, after invocation of %scl_install, current directory is %{bulidroot}/%{scl_prefix} which is not common.

I think such macro should not alter the current directory.

Issue.

%prep
generate_some_file  >foo

%install 
install foo %{buildroot}...


The install command fails because "foo" is not found in the current directory.


The current workaound is to install files (ex: the "enable" script) before %scl_install, which doesn't seems correct because
- before %scl_install the SCL tree doesn't exists yet (requiring to create the %{buildroot}%{_scl_scripts} dir first)
- %scl_install is designed to create the SCL tree
- after %scl_install, the SCL tree exists, and so, seems the right place to install additional files.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.