https://bugzilla.redhat.com/show_bug.cgi?id=1444925
Tomas Orsava <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Tomas Orsava <[email protected]> --- > > > While a reverse soft dependency wouldn't hurt anything, why would you want > > > it? > > > > Because then when normal humans want to build Python packages, they don't > > have to care that this split happened. We probably have to edit all the > > Fedora packages anyway, because weak deps are disabled in mock builds. > > Either that, or python3-devel gains a Requires on python3-rpm-generators, > > which would allow us to not have to mass edit the spec files. I'd probably > > go for the latter, personally, because then it's a "nothing changes" > > scenario everywhere. > > I see. > > Yes, there are two main ways to do this. One is to add the generators build > dependency to every Python package (or more precisely, every Python package > whose maintainer wishes to use this feature), which I think is more flexible > and is what was done for Perl but would be a massive undertaking. Another > is to add that dependency to python*-devel which is what the Python team > plans to do, from what I heard. So it should be relatively painless. Correct, that's exactly how we plan to implement this. Both python2-devel and python3-devel will have a Requires: python-rpm-generators. And the python-rpm-generators will be a Python 3—only package, so in essence you'll need Python 3 in the buildroot if you will want to build a Python 2 package. (That is how it is now anyway, so it's essentially a no-change change for Python 2.) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected]
