One annoying difference between packaging for Fedora and EPEL7 (and probably older) is the fact that Python packages in Fedora are required to provide "python2-foo" whereas many EL7 packages don't. This leads to ifdefs and unpleasantness, and kind of complicates our ability to hide some details behind macros.
As I see it, the easiest way to hide this (besides RH maintainers updating those packages with the extra Provides:) is to add a bunch of empty packages named "python2-foo" which have nothing but a dependency on "python-foo". I can get a review process exception from FPC and script up the import of these things pretty trivially. The question is: would anyone object to this? Obviously we'll have to have some way of detecting any conflicts which might arise, which can be done pretty easily with some scripting. Even just getting python2-setuptools in would eliminate a lot of cruft. There are, I believe, 166 packages which might need this, though we don't have to add them all at once if that makes things more palatable. And if there's a need to discuss this at a meeting, could someone add it to the agenda (and remind me of the meeting time)? - J< _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
