➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients a.badger, antonio, asandvig, eric.araujo, jaraco, johnkeyes, matheus.v.portela, r.david.murray, tarek, xiscu
Date 2014-04-05.12:52:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1396702334.45.0.791347691546.issue809163@psf.upfronthosting.co.za>
In-reply-to
Content 
I decided to test my proposition. It seems that simply specifying / for %files leads to the RPM including parent directories. Here's the output I get when running my test with the sed workaround:

$ rpm -q -filesbypkg -p dist/issue21153-package-0.0.0-1.noarch.rpm
issue21153-package        /usr/local/lib/python2.7/dist-packages/issue21153_package-0.0.0.egg-info
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/__init__.py
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/__init__.pyc
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/__init__.pyo
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/file with spaces.py
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/file with spaces.pyc
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/file with spaces.pyo

If instead I apply the no-record patch (attached), I can run bdist_rpm (not using sed workaround) without errors, but the resulting RPM has more directories specified:

$ rpm -q -filesbypkg -p dist/issue21153-package-0.0.0-1.noarch.rpm
issue21153-package        /
issue21153-package        /usr
issue21153-package        /usr/local
issue21153-package        /usr/local/lib
issue21153-package        /usr/local/lib/python2.7
issue21153-package        /usr/local/lib/python2.7/dist-packages
issue21153-package        /usr/local/lib/python2.7/dist-packages/issue21153_package-0.0.0.egg-info
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/__init__.py
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/__init__.pyc
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/__init__.pyo
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/file with spaces.py
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/file with spaces.pyc
issue21153-package        /usr/local/lib/python2.7/dist-packages/pkg/file with spaces.pyo

Perhaps that's acceptable. If it is, it makes the code simpler and cleaner.

Can someone comment on the impact of the presence of those parent directories in the RPM?
History
Date User Action Args
2014-04-05 12:52:14jaracosetrecipients: + jaraco, tarek, antonio, eric.araujo, a.badger, r.david.murray, xiscu, asandvig, johnkeyes, matheus.v.portela
2014-04-05 12:52:14jaracosetmessageid: <1396702334.45.0.791347691546.issue809163@psf.upfronthosting.co.za>
2014-04-05 12:52:14jaracolinkissue809163 messages
2014-04-05 12:52:13jaracocreate