On Oct 4, 2010, at 3:49 PM, Toshio Kuratomi wrote:
> On Mon, Oct 04, 2010 at 08:35:00PM +0200, Mathieu Baudier wrote:
>> Hello Kevin,
>>
>>> Reviewers and submitters of new packages welcome. :)
>>
>> I had to rebuild the following two packages so that they are python26 modules:
>>
>> python26-mod_wsgi
>>
http://elgis.argeo.org/repos/testing/5/elgis/SRPMS/repoview/python26-mod_...
>>
> mod_wsgi will need some work above and beyond simply rebuilding so that we
> can get the python-library-it's-built-against right. When we add mod_wsgi
> we'd have:
>
> mod_python
> mod_wsgi
> python26-mod_wsgi
>
> I believe that a later version of mod_wsgi can also be built against
> python-3.x so then we'd also have python3-mod_wsgi
>
> In Fedora we'd probably handle this with the apache config files that check
> whether incompatible modules are loaded and if not, then load the module.
>
> In EPEL, maybe you want to allow explicit Conflicts tags to take care of
> this case? (It would be a difference between Fedora and EPEL packaging
> guidelines but it may make sense.)
This same issue/question came up in my review for mod_python26:
https://bugzilla.redhat.com/show_bug.cgi?id=638362
Originally I had an explicit 'Conflicts: mod_python' which was inherited from the
package in IUS (based on IUS policy). The packages conflict because they both provide
python_module. As noted in the ticket... even if mod_python26 was patched to work
side-by-side with mod_python... all of the Apache directives provided by python_module
and/or python26_module would still conflict.... meaning they can't be installed and
run simultaneously. The options seem to be:
* Make the package explicitly conflict
* Add an IfModule check for python_module, and if it isn't already loaded then load
from mod_python26
To me, the first option is very clear and makes sense. From a users perspective... if
they install mod_python26 while mod_python is installed... they may be a bit confused as
to why mod_python26 just "doesn't work".
<nod> -- In Fedora we want to steer clear of Conflicts so we want to go
with
the second option but: 1) There's less versions of python there (only
a single python2 and a single python3) and 2) EPEL has a different audience
than Fedora with different needs. I think this is definitely something that
EPEL could ponder upon and write into the EPEL-specific Guidelines as
a difference.
-Toshio