[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: mod_wsgi

On Mon, Mar 08, 2010 at 01:13:01PM -0700, Stephen John Smoogen wrote:
> On Mon, Mar 8, 2010 at 11:20 AM, Josh Kayse <josh kayse gtri gatech edu> wrote:
> > I have recently acquired mod_wsgi commit permissions and am going through
> > some of the open bugs for it on bugzilla.  According to [1], and from my
> > testing, mod_wsgi and mod_python conflict resulting in apache segfaulting.
> >  The policy currently states that no packages in EPEL may conflict with a
> > package from Red Hat Base.  Technically, mod_wsgi and mod_python conflict
> > with each other, but mod_python is optional.
> Oi this is where lawyers are born.. because it looks like we are going
> to have enough corner cases that the policy is going to be 10 miles
> long to cover them all.
> EPEL packages can Conflict with RHEL-AP packages, but they can't willy
> nilly replace them. I would rather have an explicit conflict with
> mod_wsgi and mod_python in packages than have broken systems. Would a
> Conflicts cause any other issues between two repositories?
Question: For mod_wsgi/mod_python Can we do something like this (note:
I don't know what the real apache syntax would be or if it's quite

<IfNotModule mod_python.c>
LoadModule mod_wsgi.so

Note that this can still cause breakage if apache parses mod_python's
LoadModule after mod_wsgi's though.


Attachment: pgpzILYZ1h0lX.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]