Author jaraco
Recipients a.badger, antonio, asandvig, eric.araujo, jaraco, johnkeyes, matheus.v.portela, r.david.murray, tarek, xiscu
Date 2014-04-05.12:22:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1396700536.12.0.793514553139.issue809163@psf.upfronthosting.co.za>
In-reply-to
Content
In issue21153, I explored this problem as well, before being aware of this issue. I had searched for bdist_rpm.

I've since confirmed that the sed approach is viable. For example, the following works around the issue by overriding the install_script with the sed technique:

$ cat > install.txt
python setup.py install -O1 --root=$RPM_BUILD_ROOT --record=INSTALLED_FILES
sed -i -e 's/.*/"\0"/' INSTALLED_FILES

$ python setup.py bdist_rpm --install-script install.txt

I agree that sed can probably be assumed to be present, though it would be nicer not to depend on it.

It may also be possible not to have to list the files explicitly. In reading the rpm docs (http://www.rpm.org/max-rpm/s1-rpm-inside-files-list-directives.html), I discovered that rpm will traverse a directory, adding it and its contents. Perhaps the whole routine of recording installed files and then listing them explicitly can be replaced by simply referencing the build root.
History
Date User Action Args
2014-04-05 12:22:16jaracosetrecipients: + jaraco, tarek, antonio, eric.araujo, a.badger, r.david.murray, xiscu, asandvig, johnkeyes, matheus.v.portela
2014-04-05 12:22:16jaracosetmessageid: <1396700536.12.0.793514553139.issue809163@psf.upfronthosting.co.za>
2014-04-05 12:22:16jaracolinkissue809163 messages
2014-04-05 12:22:15jaracocreate