I have been adding this to the config.layout
# Adopt layout using /opt (read-only) filesystem conventions on AIX
# Standard executables in /opt (shareable)
# man pages at AIX standard location (/usr/share/man)
# editable files, scripts in /etc and /var
<Layout AIX>
prefix: /opt/apache2
exec_prefix: /opt/apache2
bindir: ${exec_prefix}/bin
sbindir: ${exec_prefix}/sbin
libdir: ${exec_prefix}/lib
libexecdir: ${exec_prefix}/libexec
mandir: /usr/share/man
sysconfdir: /etc+
datadir: /var+
installbuilddir: ${datadir}/build
errordir: ${datadir}/error
iconsdir: ${datadir}/icons
htdocsdir: ${datadir}/htdocs
manualdir: ${datadir}/manual
cgidir: ${datadir}/cgi-bin
includedir: ${prefix}/include
localstatedir: /var+
runtimedir: ${localstatedir}/run
logfiledir: ${localstatedir}/logs
proxycachedir: ${localstatedir}/proxy
</Layout>
I am hoping that this will work well supporting WPAR environments as well:
/opt, ideally, works read-only for multiple systems
/etc and /var are local to regular systems (stand-alone and LPAR servers)
So, my question about this proposed layout: are there any files in /opt
that need to be modified on a "per-system" basis?
Finally, as a distributeable I would be creating an "installp", or AIX
legacy package as this, imho, works better than RPM on AIX (and I know it
better ;) )
regards,
Michael
On Sun, Jan 29, 2012 at 11:01 PM, Graham Leggett <minf...@sharp.fm> wrote:
> On 29 Jan 2012, at 11:17 PM, Michael Felt wrote:
>
> > FYI - compiled 2.2.22 and 2.4.0 with no issues on AIX. Working on making
> an installable package (aka binary package). Is there any interest for this
> here, or is just a "fun" exercise for myself?
>
> What does this involve? Anything that makes an end user's life easier is
> welcome, including packaging up properly for an OS so that it's possible to
> deploy httpd in a standard way.
>
> Keep in mind the config.layout file, and --enable-layout option to
> ./configure, which will put all the various files in the right place
> directly. This removes the need to fiddle about trying to move files around
> during packaging, just tell httpd where they need to be and you're done.
>
> Regards,
> Graham
> --
>
>
