rahul wrote:
>
> | A draft version of Apache modules is present in
> | http://wikis.sun.com/display/WebStack/ApacheModulesARC
> Apache modules distribution with Solaris SXDE
Nit: s/Solaris SXDE/OpenSolaris/g
> /usr/apache2/libexec/mod_jk.so
> /usr/apache2/libexec/mod_fcgid.so
> /usr/apache2/libexec/mod_security2.so
>
> /usr/apache2/libexec/${ISAINFO}/mod_jk.so
> /usr/apache2/libexec/${ISAINFO}/mod_fcgid.so
> /usr/apache2/libexec/${ISAINFO}/mod_security2.so
These (and in various other places in the doc) need to be updated to
match the apache layout of 2007/586 (/usr/apache2/2.2/libexec).
> 4. Packaging and Delivery
> The modules will be delivered under the cluster SUNCapch2m. This cluster
I don't know how relevant these clusters will be in IPS world
(hopefully, not) so I'd probably not highlight it in this spec (it'll
be in your packageRTI though).
> will package SUNWapch2mfcgid, SUNWapch2mjk and SUNWapch2msecurity
> respectively.
As with the mod_php (earlier thread today), since these are delivering
into apache 2.2 specifically (into /usr/apache2/2.2/libexec), the
packages should reflect that tie and mirror the apache package name
prefix of "SUNWapch22". And for consistency with 2007/656, I'd go with
SUNWapch22m-fcgid, SUNWapch22m-jk and SUNWapch22-msecurity.
Now, here's the larger issue I'd like to see discussed: The existing
SUNWapch22u delivers quite a few modules into /usr/apache2/2.2/libexec
including larger ones like mod_perl, etc.
What makes mod_jk.so, mod_fcgid.so and mod_security2.so substantially
different? Why would each of these be delivered in its own package
instead of inside SUNWapch22u as most of these other modules?
One good reason I can think of it is dependencies. To pick one example
that is not part of this case, mod_ruby is one that (when we get to it
later) surely should be delivered as its own package because it
depends on ruby and there are people who want to use apache but don't
need ruby. So that makes sense.
So, for the three in this case, do they have such dependencies that
warrant individual packaging? What are the dependencies for each one?
For the ones which don't add any special dependencies, I'd rather see
them in SUNWapch22u along with the rest of the mostly self-contained
modules.
> Aapche modules imports interfaces from
"These apache modules"..
--
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
