The following link contains a webrev (that Seema and I have worked on) for 
integrating Apache 2.2.6 (PSARC/2007/586) into SFW/Web Stack.

http://cr.opensolaris.org/~arvi/apache2/

Please review the changes. We'd appreciate it if we could get review comments 
from folks in the sfwnv community by the end of this week (11/9)

Attached is a high-level description of the diffs.

Thanks,
Arvi
 
 
This message posted from opensolaris.org
-------------- next part --------------
Update the version of Apache2 in SFW from 2.2.3 to 2.2.6.

As detailed in PSARC/2007/586, the directory hierarchy henceforth for 
Apache 2.2.x installations in SXDE now includes an additional level 
corresponding to the major.minor version. e.g. /usr/apache2/2.2/bin, 
/etc/apache2/2.2 etc

Three new packages - SUNWapch22d, SUNWapch22r and  SUNWapch22u - replace
the existing SUNWapch2d, SUNWapch2r and SUNWapch2u packages in SFW.

This webrev builds and delivers both the 32-bit and 64-bit versions of the
prefork and worker MPMs of the Apache HTTP Server 2.2.6. The prefork build
uses apr and apr-util built by the worker build.

This webrev removes the dependency of the Apache2 build process requiring that
Apache2 be installed on the build machine. Previously, the problem was that
scripts like apxs, even when run from the proto area would still return paths
that pointed to the final install area i.e. /usr/apache2/bin etc. 
Now, apxs, apr-1-config, apu-1-config have logic that determines the 
installation root using the directory in which the script resides. This 
installation root is then prefixed to any paths that those scripts return.

Previously:
% pwd
/export/home/xxxx/php/proto/root_sparc/usr/apache2/bin
% ./apxs -q LIBDIR
/usr/apache2/lib

% pwd
/usr/apache2/bin
% ./apxs -q LIBDIR
/usr/apache2/lib

Now:
% pwd
/export/home/arvind/20071102-apache/proto/root_i386/usr/apache2/2.2/bin
% ./apxs -q LIBDIR
/export/home/arvind/20071102-apache/proto/root_i386/usr/apache2/2.2/lib

% pwd
/usr/apache2/2.2/bin
% ./apxs -q LIBDIR
/usr/apache2/2.2/lib

Now, modules like subversion, php5 etc can invoke these scripts from within
the proto area and have them return paths back into the proto area.

Patches and scripts that vary depending on the value of $(MACH64) are in
the apache2/Solaris/template directory. The actual patches/scripts used
by the build are generated from these templates by the create_solaris_patches
target in apache2/Makefile.sfw.

apache2/install-apache has been renamed as apache2/install-apache2 and an 
additional script - apache2/install-apache2-64 - has been added to install
the 64-bit binaries in the appropriate (i.e $(MACH64)) sub-directories.

apache2/apache.build.env contains common variables that were hardcoded 
across the build machinery of apache2-modperl, php5 and subversion.

Reply via email to