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 nijel
Recipients
Date 2004-02-04.21:33:33
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=192186

It's pripary purpose is IMHO to allow building of rpms when
you distribute some python stuff. It is good for this case.

The problem for distributions, is that all packages need to
be handled same way (in case they use some automatically
building system), so you can not differ whether it is
packaged some python stuff or kernel. So separate spec file
and sources is the only solution. Generating spec file
doesn't help much as it can get changed every version and
vendor has own additional information in spec file, which
would require hand merging.

Another idea I just got is to generate just file list using
separate bdist_rpm and use it separately, but I'm not sure
whether it is doable - information about file list is not
probably available there, is it?

It would be used like:

python setup.py install --root=$RPM_BUILD_ROOT
python setup.py bdist_rpm --filelist=INSTALLED_FILES
History
Date User Action Args
2007-08-23 15:27:44adminlinkissue755286 messages
2007-08-23 15:27:44admincreate