stas        2004/03/25 17:17:08

  Modified:    perl-framework/Apache-Test/lib/Apache TestMM.pm
               perl-framework/Apache-Test Changes
  Log:
  explain where to get the list of config options suitable for passing to
  Makefile.PL, and their usage
  Submitted by: David Wheeler <[EMAIL PROTECTED]>
  
  Revision  Changes    Path
  1.32      +21 -6     
httpd-test/perl-framework/Apache-Test/lib/Apache/TestMM.pm
  
  Index: TestMM.pm
  ===================================================================
  RCS file: 
/home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/TestMM.pm,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -u -r1.31 -r1.32
  --- TestMM.pm 4 Mar 2004 05:51:31 -0000       1.31
  +++ TestMM.pm 26 Mar 2004 01:17:08 -0000      1.32
  @@ -164,12 +164,13 @@
     Apache::TestMM::filter_args();
     WriteMakefile(...);
   
  -When C<WriteMakefile()> is called it parses C<@ARGV>, hoping to find special
  -options like C<PREFIX=/home/stas/perl>. C<Apache::Test> accepts a lot of
  -options of its own. When C<Apache::TestMM::filter_args()> is called, it
  -removes any C<Apache::Test>-specific options from C<@ARGV> and stores them
  -internally, so when C<WriteMakefile()> is called they aren't in C<@ARGV> and
  -thus won't be processed by C<WriteMakefile()>.
  +When C<WriteMakefile()> is called it parses C<@ARGV>, hoping to find
  +special options like C<PREFIX=/home/stas/perl>. C<Apache::Test>
  +accepts a lot of configuration options of its own. When
  +C<Apache::TestMM::filter_args()> is called, it removes any
  +C<Apache::Test>-specific options from C<@ARGV> and stores them
  +internally, so when C<WriteMakefile()> is called they aren't in
  +C<@ARGV> and thus won't be processed by C<WriteMakefile()>.
   
   The options can be set when F<Makefile.PL> is called:
   
  @@ -190,6 +191,20 @@
     %Apache::TestConfig::Argv = qw(apxs /path/to/apxs);
   
   which is going to be used by the C<Apache::Test> runtime.
  +
  +The other frequently used options are: C<-httpd>, telling where to
  +find the httpd (usually when the C<-apxs> option is not used),
  +C<-libmodperl> to use a specific mod_perl shared object (if your
  +mod_perl is built as DSO), C<-maxclients> to change the default number
  +of the configured C<MaxClients> directive, C<-port> to start the
  +server on a specific port, etc. To get the complete list of available
  +configuration options and their purpose and syntax, run:
  +
  +  % perl -MApache::TestConfig -le 'Apache::TestConfig::usage()'
  +
  +You may wish to document some of these in your application's F<README>
  +file, especially the C<-apxs> and C<-httpd> options.
  +
   
   =head2 C<generate_script>
   
  
  
  
  1.114     +2 -0      httpd-test/perl-framework/Apache-Test/Changes
  
  Index: Changes
  ===================================================================
  RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/Changes,v
  retrieving revision 1.113
  retrieving revision 1.114
  diff -u -u -r1.113 -r1.114
  --- Changes   25 Mar 2004 01:31:29 -0000      1.113
  +++ Changes   26 Mar 2004 01:17:08 -0000      1.114
  @@ -8,6 +8,8 @@
   
   =item 1.10-dev
   
  +improved docs [David Wheeler <[EMAIL PROTECTED]>]
  +
   Add a virtual method Apache::TestRun::pre_configure, and fix the
   documentation to say that subclasses must not forget to run the
   superclass' method. [Stas]
  
  
  

Reply via email to