https://bugzilla.redhat.com/show_bug.cgi?id=1444925 --- Comment #12 from Tomas Orsava <torsava@xxxxxxxxxx> --- (In reply to Igor Gnatenko from comment #10) > * Why subpackage is named as python3-? It doesn't make any sense for me. One RPM/subpackage can contain only Python 2 or Python 3 compiled files, not both at the same time. There was a discussion about providing both Python 2 and Python 3 subpackages, but with Python 2 EOL in sight we decided it wasn't necessary. Instead `python2-devel` will depend on `python3-rpm-generators`, which will mean you will drag Python 3 into the buildroot to build Python 2 packages, however we decided that isn't an issue. > * What about adding Conflicts for different versions of RPM? This will make > sure that we update it along with RPM (since upstream is same). I don't believe there really is a need to tightly couple them like so. It would complicate updating and building of both rpm and this package. > * Why not to call package python-generators? Same way as we did it with perl. There is a package called `python-rpm-macros` so I chose to follow it's naming precedent. > * What's the migration plan? Will we add Requires to rpm-build or will ask > packagers to add BuildRequires: python-generators or ...? Currently all Python packages have to have a BuildRequires on pythonX-devel. So the migration plan is to add a Requires: python3-rpm-generators to both devel subpackages. That way nothing will change from the point of view of individual packages. -- 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 -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
