Issues currently under discussion for apache integration:
[Tue Sep 11 2007]
(Note: Wherever it reads "/apache2/", interpret that to mean either
"/apache2/" or "/apache2/[version]/" depending on the resolution of
the first issue.)
OPEN: Support for concurrent versions on disk
- 2007/169 case had /usr/apache2 (and corresponding places in /etc and /var)
overwriting the [binary incompatible] 2.0 that used to be there.
- Much discussion on whether to stay the course or permit minor releases
of 2.x to coexist
- Maybe version at the minor lever "/usr/apache2/2.2/" instead of full
version to avoid tons of versions and config dirs and having to migrate
config every time there is a set of bug fixes (e.g. 2.2.4 -> 2.2.6)
- Desire to support 2.4 in S11 timeframe? (assuming it is incompatible)
(modules may require recompilation, so overwriting /usr/apache2 renders
them unusable)
- There is significant support for both approaches.
Additional details to track:
- If /usr has versions should /etc & /var too? (Yes)
- Package names also need to reflect the versioning
OPEN: libexec location vs. apxs
- apxs has various options (e.g. -i) which auto-install the compiled
module. apxs assumes the destination is the libexec directory.
- This is in /usr/apache2/libexec/ and contains all the mod_*.so files
shipped by the distribution, so it belongs under /usr
- But /usr can be read only (e.g. zones) so that doesn't work.
(it might also be shared across zones wanting to run different modules
of the same name)
-------------------------------------------------------------------------------
DEFER: 32/64 bit cohabitation
Apache creates include files at build time which embed details about
the build - such as 32 vs 64 bit-ness. This means there isn't a single
set of include files for all binaries. Not decided how to handle this.
- Ideally this should be fixed (and contribute back upstream)
- Otherwise the file layout will need to accomodate these duplicates
Not enough investigation done to properly address this yet. Initial
project will deliver 32bit only.
-------------------------------------------------------------------------------
CLOSED: startup attribute configuration
Configuration for choices which are needed prior to startup (not in
in httpd.conf). Known examples are:
- MPM choice (worker, threaded)
- 32 or 64bit server
- CLOSED: These are configured as smf attributes. Arvind sketched ideas
on how it will work for both the formal start/enable interface (smf)
as well as apachectl.
- REOPEN: Recent discussions seem to have reopened topic on the list,
need closure.
- CLOSED: They are indeed smf attributes for the apache2 service (svcprop)
CLOSED: conf.d (and other directory names)
There were various proposals on directory name changes but the
consensus was that names should not change unless there is a strong
reason.
- Keeping libexec as it has been
- The common name for the directory containing .conf files is conf.d
so we are adopting this convention: /etc/apache2/conf.d
- There is no /etc/apache2/extra
- Samples copied as-is from the source distro will continue to be in
/etc/apache2/original/extra/ (no change)
CLOSED: Support both worker and prefork MPM
CLOSED: Move /var/apache2/build/ to /usr/apache2/build/ instead.
The content does not change during runtime so living under /var is
not necessary and the move is driven by the fact that apxs assumes
it is under /usr... (It was originally placed in /var.. on the
assumption that contents needed to change at runtime)
CLOSED: Retain include foo.conf lines for every foo as well as include
*.conf (mention in comments to not uncomment both, which would cause
warnings if done).
CLOSED: Need to provide default httpd.conf that Just Works (out of box).
--
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
