>>>>> "CS" == Charalampos Stratakis <cstratak@xxxxxxxxxx> writes: CS> On a relevant note, python packaging guidelines are soon subject for CS> a change in regards to that [0] CS> [0] https://pagure.io/packaging-committee/issue/753 Please note that the ticket there started off as a strong discouragement of python2 packaging, but what was actually approved (and hopefully today will be written into the guidelines by me) is simply an extra note that maintainers are not required to package for python2 if they don't want to (which really isn't a change in packaging policy at all). So don't read the ticket title and believe that FPC has approved a blanket ban of python2 subpackages. To be completely honest, if someone wants to drop a python2 subpackage, that's their prerogative but it does bring up an interesting question. Normally if someone wants to orphan a package, they're welcome to do so and others are welcome to pick it up. But this is about removing a subpackage. If PackagerA wants to drop python2, but PackagerB wants to volunteer to maintain it, the only options I see are: * PackagerB offers to co-maintain the package, which will result in PackagerA having to deal with the python2 subpackage anyway. * The python2 subpackage gets generated by a separate python2-foo source RPM that PackagerB maintains, and the original source package becomes completely free of python2 stuff. It may be useful to see if FPC will approve a blanket exception to the review process for splitting python2-* source packages out of python-* source packages, so that bit of bureaucracy can be skipped. - J< _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
