| > 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).
I hope it can provide a way of grouping when the user selects packages
to install from the SXDE DVD.
| > 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.
updated.
| 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.
Even mod_perl that we bundle today, has the same issues.
It delivers the entire perl lib into /usr/apache2/2.2/lib/perl. It is
even more interesting because - of 4 modes that apache can work
32/64 and prefork/worker, mod_perl will work only with 32/prefork. (And
this is because the perl installed in SFW is a pure 32 bit single threaded
app.) [And for some one who wants to just use say - Ruby On Rails, mod_perl
does not really matter.]
| So, for the three in this case, do they have such dependencies that
| warrant individual packaging? What are the dependencies for each one?
Except for PCRE for mod_security, there aren't any other dependencies.
| 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.
I had mentioned my concern in the earlier mail. I would prefer the other
modules (svn/perl) that are not part of main apache source also to be kept
in different packages.
Updated version of the ARC document below
===========================================================================
Apache modules distribution with OpenSolaris
15 November 2007
1. Summary and motivation
1.1. Introduction
This FastTrack delivers Apache modules mod_jk, mod_fcgid and mod_security
to the Apache2 bundled with sfw stack.
Modules allow Apache to integrate and provide functionality
during runtime that were not available during compile time.
This FastTrack integrates the most recent stable release of
mod_jk[1] tomcat-connectors-1.2.25, mod_fcgid[2] 2.2 and
mod_security[3] 2.1.3
This case seeks Minor Release Binding.
2. Technical issues
2.1. Key objects
/usr/apache2/2.2/libexec/mod_jk.so
/usr/apache2/2.2/libexec/mod_fcgid.so
/usr/apache2/2.2/libexec/mod_security2.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_jk.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_fcgid.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_security2.so
2.2 Versioning
mod_jk, mod_fcgid and mod_security have a single active release. (There was
a module named mod_jk2 which was deprecated. It was not the successor to
mod_jk.)
It is not possible to query the modules to find out their versions. The only
way to do that is to look at the package description for the package
including it.
2.2 Directory Naming and Structure
This project delivers the shared libraries of 32 bit and 64 bit into
/usr/apache2/2.2/libexec and /usr/apache2/2.2/libexec/${ISAINFO}/
directories of the
apache. This is in keeping with the approach taken by the Apache2
integration
project for OpenSolaris.
3. Documentation
The modules mod_jk, mod_fcgid and mod_security do not install documentation
into apache though they come with some documentation in their source. The
recommended way to access their documentation is to look at their websites
(mod_fcgid[4] ,mod_jk[5] and mod_security[6]).
4. Packaging and Delivery
The modules will be delivered under the cluster SUNCapch22m. This cluster
will package SUNWapch22m-fcgid, SUNWapch22m-jk and SUNWapch22m-security
respectively.
5. Interfaces
5.1. Interface Stability
mod_jk, mod_fcgi and mod_security can be considered to have the same
interface
stability of apache (i.e interface directives can change during releases.)
since
they are apache modules.
5.2. Imported Interfaces
These Aapche modules imports interfaces from
NAME STABILITY NOTES
Apache2 Uncommitted PSARC/2007/586/
LDAP Uncommitted PSARC/2000/362/
PCRE Uncommitted PSARC/2007/164/
5.3. Exported Interfaces
NAME STABILITY NOTES
/usr/apache2/2.2/libexec/mod_jk.so Uncommitted Library
location
/usr/apache2/2.2/libexec/mod_fcgid.so Uncommitted Library
location
/usr/apache2/2.2/libexec/mod_security.so Uncommitted Library
location
/usr/apache2/2.2/libexec/${ISAINFO}/mod_jk.so Uncommitted Library
location
/usr/apache2/2.2/libexec/${ISAINFO}/mod_fcgid.so Uncommitted Library
location
/usr/apache2/2.2/libexec/${ISAINFO}/mod_security.so Uncommitted Library
location
6. References
1. http://fastcgi.coremail.cn/
2. http://tomcat.apache.org/connectors-doc/
3. http://www.modsecurity.org/projects/modsecurity/apache/index.html
4. http://fastcgi.coremail.cn/doc.htm
5. http://tomcat.apache.org/connectors-doc/generic_howto/quick.html
6. http://www.modsecurity.org/documentation/index.html
