Apache explicitly supports a number of different layouts for files out of
the box (and provides support for you to roll your own very easily). From
the manual:
The second, and more flexible way to configure the install path locations
for Apache is using the config.layout file. Using this method, it is
possible to separately specify the location for each type of file within the
Apache installation. The config.layout file contains several example
configurations, and you can also create your own custom configuration
following the examples. The different layouts in this file are grouped into
<Layout FOO>...</Layout> sections and referred to by name as in FOO. --enable-layout=LAYOUT Use the named layout in the
config.layoutfile to specify the installation
paths.
Maybe pg could benefit from something similar?
cheers
andrew
----- Original Message -----
From: "scott.marlowe" <scott.marlowe@ihs.com>
Sent: Thursday, February 13, 2003 4:07 PM
[snip]
> If I do a .tar.gz install of apache, I get /usr/local/apache/conf, which
> is not the standard way you're listing. If I install openldap from
> .tar.gz, I get a /usr/local/etc/openldap directory, close, but still not
> the same. The fact is, it's the packagers that put things into /etc and
> whatnot, and I can see the postgresql RPMs or debs or whatever having that
> as the default, but for custom built software, NOTHING that I know of
> builds from source and uses /etc without a switch to tell it to, just like
> postgresql can do now.
