Contemplating ITP-ing apache 2. Wondering about layout.

[Charles Wilson]

Gerrit P. Haase wrote:
> Max Bowsher wrote:
> 
>> I'm contemplating ITP-ing apache 2.
>>
>> It seems that practically every distribution has it's own favourite 
>> way to lay out directories of apache. Does anyone have any thoughts on 
>> how to deal with this?
> 
> 
> 
> #   Cygwin 1.x layout
> <Layout Cygwin>
>     prefix:
>     exec_prefix:   ${prefix}/usr
>     bindir:        ${exec_prefix}/bin
>     libdir:        ${exec_prefix}/lib
>     libexecdir:    ${exec_prefix}/lib/apache2/modules
>     includedir:    ${exec_prefix}/include/apache2
>     sbindir:       ${exec_prefix}/sbin
>     sysconfdir:    ${prefix}/etc/apache2
>     installbuilddir: ${prefix}/share/apr-build
>     mandir:        ${exec_prefix}/share/man
>     infodir:       ${exec_prefix}/share/info
>     localstatedir: ${prefix}/var
>     proxycachedir: ${localstatedir}/cache/apache2/proxy
>     runtimedir:    ${localstatedir}/run
>     logfiledir:    ${localstatedir}/log/apache2
>     datadir:       ${prefix}/var/www
>     cgidir:        ${datadir}/cgi-bin
>     errordir:      ${datadir}/error
>     htdocsdir:     ${datadir}/default-site/htdocs
>     iconsdir:      ${datadir}/icons
>     manualdir:     ${htdocsdir}/manual
> </Layout>

I wonder if apache is one of those FEW packages that should be placed in 
its own /opt/apache2/ heirarchy (perhaps with 
localstatedir=/opt/apache2/var as a symlink to /var/ -- NOT /usr/var)

Or would that make building the various addon modules too difficult?

Just a thought.

--
Chuck