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 loewis
Recipients ebfe, forest, jbaker, kiilerix, loewis, nshmyrev, pitrou, tarek, twegener
Date 2009-03-01.06:12:39
SpamBayes Score 2.4021233e-07
Marked as misclassified No
Message-id <>
In-reply-to <>
> What is the goal of bdist_rpm? I haven't seen that stated explicitly
> anywhere, but I assume the goal is to make a fair attempt to easily
> create usable RPMs for some software already using distutil,
> acknowledging that it might not work in all cases (because some projects
> do strange (buggy?) things) and that the RPMs probably can't be used in
> distributions directly (because they probably have their own rules and
> requirements).


> The applied patch makes it possible for bdist_rpm to work in _some_
> situations on Fedora. IMHO that is +1.

I agree. I had another complaint about that patch, though, which is
the addition of an option for not including .pyo files. I still like
to see addition of this option reverted.

> Disabling _unpackaged_files_terminate_build would IMHO be a bad
> solution. That would cause "successful" RPM builds which doesn't include
> all the files distutil installed. And FWIW I don't understand how
> __os_install_post could solve the problem.

IIUC, setting

%define __os_install_post %{___build_post}

should prevent invocation of brp-python-bytecompile.
Date User Action Args
2009-03-01 06:12:52loewissetrecipients: + loewis, twegener, nshmyrev, pitrou, forest, tarek, kiilerix, ebfe, jbaker
2009-03-01 06:12:41loewislinkissue1533164 messages
2009-03-01 06:12:39loewiscreate