stas 2003/08/18 12:16:34
Modified: src/docs/2.0/user/install install.pod
src/docs/2.0/user/intro start_fast.pod
Log:
installation instructions update
Revision Changes Path
1.44 +56 -13 modperl-docs/src/docs/2.0/user/install/install.pod
Index: install.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/install/install.pod,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- install.pod 6 Aug 2003 22:37:47 -0000 1.43
+++ install.pod 18 Aug 2003 19:16:34 -0000 1.44
@@ -194,11 +194,25 @@
=back
+=head1 Installing mod_perl from Binary Packages
+
+As of this writing only the binaries for the Win32 platform are
+available, kindly prepared and maintained by Randy Kobes.
+See the documentation on L<Win32 binaries|docs::2.0::os::win32::install>
+for details.
+
+Some RPM packages can be found using rpmfind services, e.g.:
+
+http://www.rpmfind.net/linux/rpm2html/search.php?query=mod_perl&submit=Search+...
+However if you have problems using them, you have to contact those who
+have created them.
+
=head1 Installing mod_perl from Source
Building from source is the best option, because it ensures a binary
-compatibility with Apache and Perl.
+compatibility with Apache and Perl. However it's possible that your
+distribution provides a solid binary mod_perl 2.0 package.
For Win32 specific details, see the documentation on
L<Win32 installation|docs::2.0::os::win32::install>.
@@ -237,6 +251,10 @@
% cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co modperl-2.0
+You can also try the latest CVS snapshot:
+
+http://cvs.apache.org/snapshots/modperl-2.0/
+
=back
@@ -246,15 +264,42 @@
Before you proceed make sure that Apache 2.0 has been built and
installed. mod_perl B<cannot> be built before that.
+Like any other Perl module, mod_perl is configured via the
+I<Makefile.PL> file, but requires one or more configuration options:
+
+ % perl Makefile.PL <options>
+
+where I<options> is an optional list of (key,value) pairs. Usually
+you need to use only the C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option to
+complete the build. This and other options are discussed in the
+following sections.
+
+If all Apache 2.0 files were installed under the same directory,
+mod_perl 2.0's build only needs to know the path to that directory,
+passed via the C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option:
+
% cd modperl-2.0
% perl Makefile.PL MP_AP_PREFIX=$HOME/httpd/prefork \
MP_INST_APACHE2=1
-XXX: MP_INST_APACHE2=1 should become the default
+XXX: MP_INST_APACHE2=1 should become the default, but for now add it
+too.
-I<options> an optional list of (key,value) pairs. Usually you need to
-use only the C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option to complete the
-build. This and other options are discussed in the following sections.
+However if the Apache 2.0 files are spread under different locations,
+which is the case on many distributions that provide the binary Apache
+2.0 package, other options may need to be provided. For example RedHat
+Linux system installs the httpd binary, the apxs and apr-config
+scripts all in different locations, therefore they configure mod_perl
+2.0 as:
+
+ % perl Makefile.PL MP_APXS=/path/to/apxs \
+ MP_APR_CONFIG=/another/path/to/apr-config <other options>
+
+In this case there is no need to specify the
+C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> option, since paths to the scripts
+specified by C<L<MP_APXS|/MP_APXS>> and
+C<L<MP_APR_CONFIG|/MP_APR_CONFIG>> can be used to retrieve the rest of
+the information.
=head3 Boolean Build Options
@@ -449,8 +494,8 @@
If APR wasn't installed under the same file tree as httpd, you may
need to tell the build process where it can find the executable
-C<apr-config>, which can then be used to figure out where the apr
-I<include/> and I<lib> directories can be found.
+C<apr-config>, which can then be used to figure out where the apr and
+aprutil I<include/> and I<lib/> directories can be found.
=head4 MP_CCOPTS
@@ -545,14 +590,12 @@
% make install
If you install mod_perl system wide, you probably need to become
-I<root> prior to doing the installation.
+I<root> prior to doing the installation:
+
+ % su
+ # make install
-=head1 Installing mod_perl from Binary Packages
-As of this writing only the binaries for the Win32 platform are
-available, kindly prepared and maintained by Randy Kobes.
-See the documentation on L<Win32 binaries|docs::2.0::os::win32::install>
-for details.
=head1 If Something Goes Wrong
1.15 +5 -2 modperl-docs/src/docs/2.0/user/intro/start_fast.pod
Index: start_fast.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/intro/start_fast.pod,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- start_fast.pod 6 Jun 2003 09:24:46 -0000 1.14
+++ start_fast.pod 18 Aug 2003 19:16:34 -0000 1.15
@@ -20,8 +20,11 @@
Apache and the right Perl version have to be built and installed
B<before> you can proceed with building mod_perl.
-In this chapter we assume that httpd was installed under
-I<$HOME/httpd/prefork>.
+In this chapter we assume that httpd and all helper files were
+installed under I<$HOME/httpd/prefork>, if your distribution doesn't
+install all the files under the same tree, please refer to L<the
+complete installation
+instructions|docs::2.0::user::install::install/Installing_mod_perl_from_Source>.
Now, configure mod_perl:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
