public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] apache extramodules?
@ 2003-09-10 21:13 Garrett Goebel
  2003-09-19 18:16 ` Paul de Vrieze
  0 siblings, 1 reply; 2+ messages in thread
From: Garrett Goebel @ 2003-09-10 21:13 UTC (permalink / raw
  To: 'gentoo-dev@gentoo.org'; +Cc: 'carpaski@gentoo.org'

[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]

Gentoo's Apache configuration appears to be broken.

I recently ran into a problem using the mod_perl Apache::Test module.
Apache::Test uses /usr/sbin/apxs -q LIBEXECDIR to locate libperl.so. Which
when executed returns /usr/lib/apache. However, someone doing Apache ebuilds
decided to create a second module directory for non Apache core modules
called /usr/lib/apache-extramodules. Which is where Gentoo currently
installs libperl.so. Thus breaking Apache::Test's ability to use apxs to
locate it. 

Both of these module locations are symbolically linked to appear in
/etc/apache as: 

extramodules -> ../../usr/lib/apache-extramodules 
modules -> ../../usr/lib/apache 

So the multitude of mod_php, mod_perl, mod_throttle, etc. modules all appear
to be installed in a location (extramodules) which apxs can't locate and
work with at runtime. Which I believe is kind of the whole purpose of apxs
right? 

I traded emails with Stas Beckman (mod_perl guru and author of "Practical
mod_perl" and Apache::Test). It is his opinion
(http://www.mail-archive.com/modperl@apache.org/msg35963.html) if I'm
reading it right that there should be only one LIBEXECDIR so that apxs -q
LIBEXECDIR can report correct values. I supplied him with a patch, but it is
his opinion Gentoo is broken... and that special casing things for Gentoo
would do more evil than good.

There are a sizable number of mod_* modules which would need to be fixed. To
create a list of the 59 files which currently mention extramodules I used: 

find /usr/portage|xargs grep "extramodules"|perl -pe 's/:.*//'|sort|uniq 

Note: a sizeable number of those refer to ebuilds with multiple revisions. 

Does anyone know why extramodules exists? I.e. what justifies a non-standard
apache install which breaks runtime apxs support?

--
Garrett Goebel
IS Development Specialist

ScriptPro                   Direct: 913.403.5261
5828 Reeds Road               Main: 913.384.1008
Mission, KS 66202              Fax: 913.384.2180
www.scriptpro.com          garrett at scriptpro dot com


[-- Attachment #2: Type: text/html, Size: 3223 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-dev] apache extramodules?
  2003-09-10 21:13 [gentoo-dev] apache extramodules? Garrett Goebel
@ 2003-09-19 18:16 ` Paul de Vrieze
  0 siblings, 0 replies; 2+ messages in thread
From: Paul de Vrieze @ 2003-09-19 18:16 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 661 bytes --]

On Wednesday 10 September 2003 23:13, Garrett Goebel wrote:
> Gentoo's Apache configuration appears to be broken.
>
> find /usr/portage|xargs grep "extramodules"|perl -pe 's/:.*//'|sort|uniq
>
> Note: a sizeable number of those refer to ebuilds with multiple revisions.
>
> Does anyone know why extramodules exists? I.e. what justifies a
> non-standard apache install which breaks runtime apxs support?
>

Please file a bug about this. It is indeed a problem, I don't know why 
extramodules exists, but in someway the bug should be fixed.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-09-19 18:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-09-10 21:13 [gentoo-dev] apache extramodules? Garrett Goebel
2003-09-19 18:16 ` Paul de Vrieze

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox