Mailing List Archive: Bricolage: devel

Make/install as non-root

Index | Next | Previous | View Threaded

brian at gossamer-threads

Apr 18, 2008, 5:27 PM

Post #1 of 17 (1048 views)
Permalink

Make/install as non-root

Good afternoon!

First, as this is my first actual post (after a lot of lurking), a brief
introduction: I'm the (relatively) new senior system administrator at
Gossamer Threads, working for Alex Krohn.

We run Bricolage installs in a non-root environment, and have a series
of patches and hacks to make that work. I've been cleaning it up a lot
over the last few weeks and trying to make patches to send back
upstream. The basic idea is that, short of creating the database and the
database user, the entire install should be able to be run in userspace.
I had these working against 1.10.4, and am now rewriting bits of them
against the current svn checkout.

This mostly requires minor changes; for example, getting bin/Makefile.PL
and lib/Makefile.PL to pass BRICOLAGE_ROOT as PREFIX, if that variable
is defined in config.db.

For most database-related tasks, I've had it work as the bricolage user
rather than as root (unless $> == 0).

If this seems useful, I'll send along patches and a full list of changes
once I finish adapting it to the current svn.

-Brian

david at kineticode

Apr 18, 2008, 5:33 PM

Post #2 of 17 (1022 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 18, 2008, at 17:27, Brian Smith wrote:

> First, as this is my first actual post (after a lot of lurking), a
> brief
> introduction: I'm the (relatively) new senior system administrator at
> Gossamer Threads, working for Alex Krohn.
>
> We run Bricolage installs in a non-root environment, and have a series
> of patches and hacks to make that work. I've been cleaning it up a lot
> over the last few weeks and trying to make patches to send back
> upstream. The basic idea is that, short of creating the database and
> the
> database user, the entire install should be able to be run in
> userspace.
> I had these working against 1.10.4, and am now rewriting bits of them
> against the current svn checkout.

Trunk? Awesome.

> This mostly requires minor changes; for example, getting bin/
> Makefile.PL
> and lib/Makefile.PL to pass BRICOLAGE_ROOT as PREFIX, if that variable
> is defined in config.db.

Ah, that's smart.

> For most database-related tasks, I've had it work as the bricolage
> user
> rather than as root (unless $> == 0).

Yeah, that's where it will get tricky. Stupid ident auth.

> If this seems useful, I'll send along patches and a full list of
> changes
> once I finish adapting it to the current svn.

I look forward to seeing them. And welcome!

Best,

David

brian at gossamer-threads

Apr 18, 2008, 7:26 PM

Post #3 of 17 (1018 views)
Permalink

Re: Make/install as non-root [In reply to]

Here's a few to get started with...

The only outstanding issue is that mysql.sql has a SET GLOBAL in line 31
after make dist and some CREATE TRIGGERs; that won't work as user, but
everything else does. If I temporarily grant SUPER, it'll work.

All the Postgres stuff works in userspace after patching. All patches
are from trunk as of an hour ago.

patch1.diff - just adds /usr/lib/httpd to the initial Apache module
check, which is where Apache modules reside on our servers (and I think
on Gentoo in general).

patch2.diff - adds the BRICOLAGE_ROOT / PREFIX tie-in that I mentioned
in my previous e-mail.

patch3.diff - does all the database modifications necessary for make
install to work in userspace:
* adds an extra question in the DB prober to ask if the installer
should create the database and database user;
* modifies the DB loaders so that they only load the data, not create
the databases, if create_db is 0; and
* skips the DB grant process entirely if create_db is 0

(This is the ugliest piece of what I've done here, and I'm still not
convinced it's the best way to do it. It works, but there may be better
ways to go.)

patch4.diff - makes 'make uninstall' work by warning the user, if
they're not root, that it won't be able to drop the database (and thus
just uninstalls the files).

With this -- aside from that SUPER thing -- make dist, make, make
install, and make uninstall all work. I still need to play with make
upgrade and make clone, which I plan to tackle this weekend or early
next week.

-Brian

On Fri, 2008-04-18 at 17:33 -0700, David E. Wheeler wrote:
> On Apr 18, 2008, at 17:27, Brian Smith wrote:
>
> > This mostly requires minor changes; for example, getting bin/
> > Makefile.PL
> > and lib/Makefile.PL to pass BRICOLAGE_ROOT as PREFIX, if that variable
> > is defined in config.db.
>
> Ah, that's smart.
>
> > For most database-related tasks, I've had it work as the bricolage
> > user
> > rather than as root (unless $> == 0).
>
> Yeah, that's where it will get tricky. Stupid ident auth.
>
> > If this seems useful, I'll send along patches and a full list of
> > changes
> > once I finish adapting it to the current svn.
>
> I look forward to seeing them. And welcome!
>
> Best,
>
> David
>

brian at gossamer-threads

Apr 18, 2008, 7:27 PM

Post #4 of 17 (1024 views)
Permalink

Re: Make/install as non-root [In reply to]

*sigh* I'll try that again, actually attaching the files this time . . .

-Brian

On Fri, 2008-04-18 at 19:26 -0700, Brian Smith wrote:
> Here's a few to get started with...
>
> The only outstanding issue is that mysql.sql has a SET GLOBAL in line 31
> after make dist and some CREATE TRIGGERs; that won't work as user, but
> everything else does. If I temporarily grant SUPER, it'll work.
>
> All the Postgres stuff works in userspace after patching. All patches
> are from trunk as of an hour ago.
>
> patch1.diff - just adds /usr/lib/httpd to the initial Apache module
> check, which is where Apache modules reside on our servers (and I think
> on Gentoo in general).
>
> patch2.diff - adds the BRICOLAGE_ROOT / PREFIX tie-in that I mentioned
> in my previous e-mail.
>
> patch3.diff - does all the database modifications necessary for make
> install to work in userspace:
> * adds an extra question in the DB prober to ask if the installer
> should create the database and database user;
> * modifies the DB loaders so that they only load the data, not create
> the databases, if create_db is 0; and
> * skips the DB grant process entirely if create_db is 0
>
> (This is the ugliest piece of what I've done here, and I'm still not
> convinced it's the best way to do it. It works, but there may be better
> ways to go.)
>
> patch4.diff - makes 'make uninstall' work by warning the user, if
> they're not root, that it won't be able to drop the database (and thus
> just uninstalls the files).
>
> With this -- aside from that SUPER thing -- make dist, make, make
> install, and make uninstall all work. I still need to play with make
> upgrade and make clone, which I plan to tackle this weekend or early
> next week.
>
> -Brian
>

Attachments:

patch1.diff (0.55 KB)

patch2.diff (1.04 KB)

patch3.diff (9.21 KB)

patch4.diff (0.96 KB)

david at kineticode

Apr 20, 2008, 10:29 AM

Post #5 of 17 (1019 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 18, 2008, at 19:26, Brian Smith wrote:

> Here's a few to get started with...
>
> The only outstanding issue is that mysql.sql has a SET GLOBAL in
> line 31
> after make dist and some CREATE TRIGGERs; that won't work as user, but
> everything else does. If I temporarily grant SUPER, it'll work.

So is that possible? We do need to have those settings in place for
all use of Bricolage. If they can just be limited to the Bricolage
database itself, rather than global, then that's fine.

> All the Postgres stuff works in userspace after patching. All patches
> are from trunk as of an hour ago.
>
> patch1.diff - just adds /usr/lib/httpd to the initial Apache module
> check, which is where Apache modules reside on our servers (and I
> think
> on Gentoo in general).

Crimony, I can't tell you how I hate that every fucking distribution
keeps shit in different places.

> patch2.diff - adds the BRICOLAGE_ROOT / PREFIX tie-in that I mentioned
> in my previous e-mail.
>
> patch3.diff - does all the database modifications necessary for make
> install to work in userspace:
> * adds an extra question in the DB prober to ask if the installer
> should create the database and database user;
> * modifies the DB loaders so that they only load the data, not create
> the databases, if create_db is 0; and
> * skips the DB grant process entirely if create_db is 0

Thanks. I'll take a look at these tomorrow, most likely.

> (This is the ugliest piece of what I've done here, and I'm still not
> convinced it's the best way to do it. It works, but there may be
> better
> ways to go.)

I'll take a look. The whole installer is ugly, though, so I can't say
I'm surprised.

> patch4.diff - makes 'make uninstall' work by warning the user, if
> they're not root, that it won't be able to drop the database (and thus
> just uninstalls the files).

Well, can't the user drop the database if they don't have system root,
but do have database root access? Is the latter what you meant?

> With this -- aside from that SUPER thing -- make dist, make, make
> install, and make uninstall all work. I still need to play with make
> upgrade and make clone, which I plan to tackle this weekend or early
> next week.

Awesome, thanks! "SUPER thing"?

Best,

David

bharder at methodlogic

Apr 20, 2008, 10:48 AM

Post #6 of 17 (1019 views)
Permalink

Re: Make/install as non-root [In reply to]

On Sun, Apr 20, 2008 at 10:29:17AM -0700, David E. Wheeler wrote:
> On Apr 18, 2008, at 19:26, Brian Smith wrote:
>
> >Here's a few to get started with...
> >
> >The only outstanding issue is that mysql.sql has a SET GLOBAL in
> >line 31
> >after make dist and some CREATE TRIGGERs; that won't work as user, but
> >everything else does. If I temporarily grant SUPER, it'll work.
>
> So is that possible? We do need to have those settings in place for
> all use of Bricolage. If they can just be limited to the Bricolage
> database itself, rather than global, then that's fine.
>
> >All the Postgres stuff works in userspace after patching. All patches
> >are from trunk as of an hour ago.
> >
> >patch1.diff - just adds /usr/lib/httpd to the initial Apache module
> >check, which is where Apache modules reside on our servers (and I
> >think
> >on Gentoo in general).
>
> Crimony, I can't tell you how I hate that every fucking distribution
> keeps shit in different places.

If this is overrideable via an ENV variable, that'd be excellent.

> >patch2.diff - adds the BRICOLAGE_ROOT / PREFIX tie-in that I mentioned
> >in my previous e-mail.
> >
> >patch3.diff - does all the database modifications necessary for make
> >install to work in userspace:
> >* adds an extra question in the DB prober to ask if the installer
> >should create the database and database user;
> >* modifies the DB loaders so that they only load the data, not create
> >the databases, if create_db is 0; and
> >* skips the DB grant process entirely if create_db is 0
>
> Thanks. I'll take a look at these tomorrow, most likely.
>
> >(This is the ugliest piece of what I've done here, and I'm still not
> >convinced it's the best way to do it. It works, but there may be
> >better
> >ways to go.)
>
> I'll take a look. The whole installer is ugly, though, so I can't say
> I'm surprised.
>
> >patch4.diff - makes 'make uninstall' work by warning the user, if
> >they're not root, that it won't be able to drop the database (and thus
> >just uninstalls the files).
>
> Well, can't the user drop the database if they don't have system root,
> but do have database root access? Is the latter what you meant?
>
> >With this -- aside from that SUPER thing -- make dist, make, make
> >install, and make uninstall all work. I still need to play with make
> >upgrade and make clone, which I plan to tackle this weekend or early
> >next week.
>
> Awesome, thanks! "SUPER thing"?
>
> Best,
>
> David
>

--

Brad Harder,
Method Digital Logic
http://www.methodlogic.net

brian at gossamer-threads

Apr 21, 2008, 11:12 AM

Post #7 of 17 (1011 views)
Permalink

Re: Make/install as non-root [In reply to]

On Sun, 2008-04-20 at 10:48 -0700, bharder wrote:
> > >patch1.diff - just adds /usr/lib/httpd to the initial Apache module
> > >check, which is where Apache modules reside on our servers (and I
> > >think
> > >on Gentoo in general).
> >
> > Crimony, I can't tell you how I hate that every fucking distribution
> > keeps shit in different places.
>
> If this is overrideable via an ENV variable, that'd be excellent.

Alternately, how about having the installer ask? I can throw a patch for
that today if that sounds good.

(I'm thinking -- it does its detection as best it can, but if it fails,
instead of just failing outright, it asks where the Apache module
directory is. Then I could type '/usr/lib/httpd' and off we go.)

-Brian

david at kineticode

Apr 21, 2008, 11:17 AM

Post #8 of 17 (1015 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 21, 2008, at 11:12, Brian Smith wrote:

>> If this is overrideable via an ENV variable, that'd be excellent.
>
> Alternately, how about having the installer ask? I can throw a patch
> for
> that today if that sounds good.

AFAIK, it *does* ask.

> (I'm thinking -- it does its detection as best it can, but if it
> fails,
> instead of just failing outright, it asks where the Apache module
> directory is. Then I could type '/usr/lib/httpd' and off we go.)

It does ask.

Best,

David

brian at gossamer-threads

Apr 21, 2008, 11:42 AM

Post #9 of 17 (1015 views)
Permalink

Re: Make/install as non-root [In reply to]

It asks the path to the Apache binary--which here
is /usr/sbin/httpd--but it never asks the path to the Apache
libraries/modules. So I give it the correct binary path, and then I see:

---

Extracting configuration data from `/usr/sbin/httpd -V`.
Extracting static module list from `/usr/sbin/httpd -l`.
Your Apache supports loadable modules (DSOs).
Checking for required Apache modules...
###############################################################################

The following Apache modules are required by Bricolage and
are missing from your installation:
mod_perl
mod_log_config
mod_mime
mod_alias

###############################################################################
make: *** [apache.db] Error 1
brian[at]dev32 bricolage-1.11.0 $
---

This is the case in both 1.10.4 and in the current svn trunk.

-Brian

On Mon, 2008-04-21 at 11:17 -0700, David E. Wheeler wrote:
> On Apr 21, 2008, at 11:12, Brian Smith wrote:
>
> >> If this is overrideable via an ENV variable, that'd be excellent.
> >
> > Alternately, how about having the installer ask? I can throw a patch
> > for
> > that today if that sounds good.
>
> AFAIK, it *does* ask.
>
> > (I'm thinking -- it does its detection as best it can, but if it
> > fails,
> > instead of just failing outright, it asks where the Apache module
> > directory is. Then I could type '/usr/lib/httpd' and off we go.)
>
> It does ask.
>
> Best,
>
> David
>

bharder at methodlogic

Apr 21, 2008, 11:45 AM

Post #10 of 17 (1018 views)
Permalink

Re: Make/install as non-root [In reply to]

On Mon, Apr 21, 2008 at 11:12:58AM -0700, Brian Smith wrote:
>
> On Sun, 2008-04-20 at 10:48 -0700, bharder wrote:
> > > >patch1.diff - just adds /usr/lib/httpd to the initial Apache module
> > > >check, which is where Apache modules reside on our servers (and I
> > > >think
> > > >on Gentoo in general).
> > >
> > > Crimony, I can't tell you how I hate that every fucking distribution
> > > keeps shit in different places.
> >
> > If this is overrideable via an ENV variable, that'd be excellent.
>
> Alternately, how about having the installer ask? I can throw a patch for
> that today if that sounds good.

I think a way to do a non-interactive configure would be nice. Setting an ENV variable fits the bill in this case. That way, for make(1)-based installs (ie: FreeBSD, NetBSD, OpenBSD, Gentoo, etc.), one can have an variable set for that arch, and everything will Just Work. An interactive alternative in this case is useless. If there's no ENV var (or similar -- environment vars are just the first thing I thought of, and seem both capable and simple enough), then package managers will need to start patching the installer.

> (I'm thinking -- it does its detection as best it can, but if it fails,
> instead of just failing outright, it asks where the Apache module
> directory is. Then I could type '/usr/lib/httpd' and off we go.)
>
> -Brian
>

--

Brad Harder,
Method Digital Logic
http://www.methodlogic.net

marshall at exclupen

Apr 21, 2008, 11:55 AM

Post #11 of 17 (1013 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 21, 2008, at 2:45 PM, bharder wrote:
> I think a way to do a non-interactive configure would be nice.
> Setting an ENV variable fits the bill in this case. That way, for
> make(1)-based installs (ie: FreeBSD, NetBSD, OpenBSD, Gentoo, etc.),
> one can have an variable set for that arch, and everything will Just
> Work. An interactive alternative in this case is useless. If there's
> no ENV var (or similar -- environment vars are just the first thing
> I thought of, and seem both capable and simple enough), then package
> managers will need to start patching the installer.

See dist/defaults/*. The FreeBSD/Gentoo/Debian/etc. package's
dependencies will guarantee that the Apache files are there. That
means that the installer could fall back on interactive mode without
screwing up silent installs.

--
Marshall

bharder at methodlogic

Apr 21, 2008, 12:47 PM

Post #12 of 17 (1014 views)
Permalink

Re: Make/install as non-root [In reply to]

On Mon, Apr 21, 2008 at 02:55:11PM -0400, Marshall Roch wrote:
> On Apr 21, 2008, at 2:45 PM, bharder wrote:
> >I think a way to do a non-interactive configure would be nice.
> >Setting an ENV variable fits the bill in this case. That way, for
> >make(1)-based installs (ie: FreeBSD, NetBSD, OpenBSD, Gentoo, etc.),
> >one can have an variable set for that arch, and everything will Just
> >Work. An interactive alternative in this case is useless. If there's
> >no ENV var (or similar -- environment vars are just the first thing
> >I thought of, and seem both capable and simple enough), then package
> >managers will need to start patching the installer.
>
> See dist/defaults/*. The FreeBSD/Gentoo/Debian/etc. package's
^^^^^^^^^^^^^^^
Hey Marshall, I don't know what you're referring to there...

Oh -- I see -- "inst/defaults/*" -- Yup -- that looks like it'd exactly do the job I'm thinking of. Nice ;)

> dependencies will guarantee that the Apache files are there. That
> means that the installer could fall back on interactive mode without
> screwing up silent installs.

--

Brad Harder,
Method Digital Logic
http://www.methodlogic.net

bharder at methodlogic

Apr 21, 2008, 12:52 PM

Post #13 of 17 (1011 views)
Permalink

Re: Make/install as non-root [In reply to]

On Mon, Apr 21, 2008 at 12:47:59PM -0700, bharder wrote:
> On Mon, Apr 21, 2008 at 02:55:11PM -0400, Marshall Roch wrote:
> > On Apr 21, 2008, at 2:45 PM, bharder wrote:
> > >I think a way to do a non-interactive configure would be nice.
> > >Setting an ENV variable fits the bill in this case. That way, for
> > >make(1)-based installs (ie: FreeBSD, NetBSD, OpenBSD, Gentoo, etc.),
> > >one can have an variable set for that arch, and everything will Just
> > >Work. An interactive alternative in this case is useless. If there's
> > >no ENV var (or similar -- environment vars are just the first thing
> > >I thought of, and seem both capable and simple enough), then package
> > >managers will need to start patching the installer.
> >
> > See dist/defaults/*. The FreeBSD/Gentoo/Debian/etc. package's
> ^^^^^^^^^^^^^^^
> Hey Marshall, I don't know what you're referring to there...

Although, what happens when "Linux Distro-A" needs to have it's unique configuration accounted, for? And then Distro-B, Distro-C, D, E, F, etc? How are these files referenced by the installer?

> Oh -- I see -- "inst/defaults/*" -- Yup -- that looks like it'd exactly do the job I'm thinking of. Nice ;)
>
> > dependencies will guarantee that the Apache files are there. That
> > means that the installer could fall back on interactive mode without
> > screwing up silent installs.
>
> --
>
> Brad Harder,
> Method Digital Logic
> http://www.methodlogic.net

--

Brad Harder,
Method Digital Logic
http://www.methodlogic.net

david at kineticode

Apr 25, 2008, 3:45 PM

Post #14 of 17 (973 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 18, 2008, at 19:27, Brian Smith wrote:

>> patch1.diff - just adds /usr/lib/httpd to the initial Apache module
>> check, which is where Apache modules reside on our servers (and I
>> think
>> on Gentoo in general).

Thanks. Should inst/defaults/gentoo be updated? And should a
commensurate patch be applied to support Apache 2? Applied in r8164
(rev_1_10) and r8165 (trunk).

>> patch2.diff - adds the BRICOLAGE_ROOT / PREFIX tie-in that I
>> mentioned
>> in my previous e-mail.

Thanks. Applied to rev_1_10 in r8166.

>> patch3.diff - does all the database modifications necessary for make
>> install to work in userspace:
>> * adds an extra question in the DB prober to ask if the installer
>> should create the database and database user;
>> * modifies the DB loaders so that they only load the data, not create
>> the databases, if create_db is 0; and
>> * skips the DB grant process entirely if create_db is 0
>>
>> (This is the ugliest piece of what I've done here, and I'm still not
>> convinced it's the best way to do it. It works, but there may be
>> better
>> ways to go.)

Looks okay to me. Looking at it, though, I think that we can actually
allow users to create and grant permissions to the database even if
they're not a system super user but can be a database system user. For
that to work, however, we'd need a directive to indicate whether or
not the PostgreSQL installation scripts should become the "postgres"
super user, as only the system super user can do that. Or, actually,
to only try if the script is run as root. Thoughts?

Anyway, what you had has been committed, with some minor changes from
yours truly, to trunk in r8168.

>> patch4.diff - makes 'make uninstall' work by warning the user, if
>> they're not root, that it won't be able to drop the database (and
>> thus
>> just uninstalls the files).

I can't accept this patch, unfortunately, because on many systems you
do *not* have to be root to drop a database. You have to be a database
super user, but not a system super user.

>> With this -- aside from that SUPER thing -- make dist, make, make
>> install, and make uninstall all work. I still need to play with make
>> upgrade and make clone, which I plan to tackle this weekend or early
>> next week.

Awesome, thanks!

David

david at kineticode

Apr 25, 2008, 3:48 PM

Post #15 of 17 (977 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 21, 2008, at 11:42, Brian Smith wrote:

> It asks the path to the Apache binary--which here
> is /usr/sbin/httpd--but it never asks the path to the Apache
> libraries/modules. So I give it the correct binary path, and then I
> see:
>
> ---
> ==> Probing Apache Configuration <==
>
> Extracting configuration data from `/usr/sbin/httpd -V`.
> Extracting static module list from `/usr/sbin/httpd -l`.
> Your Apache supports loadable modules (DSOs).
> Checking for required Apache modules...
> ###############################################################################
>
> The following Apache modules are required by Bricolage and
> are missing from your installation:
> mod_perl
> mod_log_config
> mod_mime
> mod_alias
>
>
> ###############################################################################
> make: *** [apache.db] Error 1
> brian[at]dev32 bricolage-1.11.0 $
> ---
>
> This is the case in both 1.10.4 and in the current svn trunk.

WTF? Why aren't the modules stored under the apache root? Sheesh.

Yeah, a directive would be good. See what I've done for environment
variables using get_default() (which also uses the defaults files) to
add a directive (and a confirmation).

Thanks,

David

marshall at exclupen

Apr 25, 2008, 4:07 PM

Post #16 of 17 (978 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 25, 2008, at 6:45 PM, David E. Wheeler wrote:
> On Apr 18, 2008, at 19:27, Brian Smith wrote:
>
>>> patch1.diff - just adds /usr/lib/httpd to the initial Apache module
>>> check, which is where Apache modules reside on our servers (and I
>>> think
>>> on Gentoo in general).
>
> Thanks. Should inst/defaults/gentoo be updated? And should a
> commensurate patch be applied to support Apache 2? Applied in r8164
> (rev_1_10) and r8165 (trunk).

I'd say inst/defaults/gentoo should be updated to use to Apache 2
exclusively. Apache 1 was removed from Gentoo in June 2007, so if
you're installing with Apache 1 on Gentoo, you're gonna have to do it
by hand anyway. Plus the defaults are really there for package makers
so that they don't have to maintain downstream patches.

FWIW, Gentoo puts Apache 2 modules in /usr/lib/apache2/modules/, but
it could use apxs instead of hard-coding it:

# apxs -q LIBEXECDIR
/usr/lib/apache2/modules

--
Marshall

david at kineticode

Apr 25, 2008, 4:28 PM

Post #17 of 17 (977 views)
Permalink

Re: Make/install as non-root [In reply to]

On Apr 25, 2008, at 16:07, Marshall Roch wrote:

> I'd say inst/defaults/gentoo should be updated to use to Apache 2
> exclusively. Apache 1 was removed from Gentoo in June 2007, so if
> you're installing with Apache 1 on Gentoo, you're gonna have to do
> it by hand anyway. Plus the defaults are really there for package
> makers so that they don't have to maintain downstream patches.

Okay. Patches welcome. ;-)

> FWIW, Gentoo puts Apache 2 modules in /usr/lib/apache2/modules/, but
> it could use apxs instead of hard-coding it:
>
> # apxs -q LIBEXECDIR
> /usr/lib/apache2/modules

Yeah, but then we'd have to rewrite the detection code to use apxs
instead of httpd. We probably should, but my two weeks is up today and
I'm pushing into Monday as it is. But if anyone wanted to take that
on, I would welcome it.

Best,

David

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com