Bug 1032451

Summary:	%scl_install change current directory
Product:	Red Hat Enterprise Linux 7	Reporter:	Marcela Mašláňová <mmaslano>
Component:	scl-utils	Assignee:	Jan Zeleny <jzeleny>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukáš Zachar <lzachar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	bkabrda, drieden, jzeleny, mizdebsk, rcollet
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	scl-utils-20130529-2.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1029515	Environment:
Last Closed:	2014-06-13 13:07:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1011360, 1029515, 1040859
Bug Blocks:	1007875

Description Marcela Mašláňová 2013-11-20 08:58:40 UTC

+++ 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.

Comment 3 Ludek Smid 2014-06-13 13:07:19 UTC

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.