[ANNOUNCE] Apache-Test 1.28

[Geoffrey Young <ge...@modperlcookbook.org>]

The URL

    http://people.apache.org/~geoff/Apache-Test-1.28.tar.gz

has entered CPAN as

  file: $CPAN/authors/id/G/GE/GEOFF/Apache-Test-1.28.tar.gz
  size: 149856 bytes
   md5: 76ca771bb9d36b6215e7f418a7fd5e9a

--Geoff


Changes since 1.27:

add need_imagemap() and have_imagemap() to check for mod_imap
or mod_imagemap [ Colm MacCarthaigh ]

shortcuts like need_cgi() and need_php() no longer spit out
bogus skip messages  [Geoffrey Young]

Adjust Apache::TestConfig::untaint_path() to handle relative paths
that don't start with /.  [Stas]

If perlpath is longer than 62 chars, some shells on certain platforms
won't be able to run the shebang line, so when seeing a long perlpath
use the eval workaround [Mike Smith <mi...@mailchannels.com>]

Location of the pid file is now configurable via the command line
-t_pid_file option [Joe Orton]

remove the mod_perl.pm entry from %INC after Apache::Test finishes
initializing itself.  because both mp1 and mp2 share the entry,
leaving it around means that Apache::Test might prevent later modules
from loading the real mod_perl module they're interested in, leading
to bad things  [Geoffrey Young]

use which("cover") to find the cover utility from Devel::Cover and run
it only if found. [Stas]

Devel::Cover magic is now fully integrated.  no more modperl_extra.pl
or extra.conf.in fiddling - 'make testcover' should be all you need
to do now [Geoffrey Young]

Implemented a magic @NextAvailablePort@ to be used in config files to
automatically allocate the next available port [Stas]

Adjust Apache::TestConfig::add_inc to add lib/ in separate call to
lib::->import at the very end of @INC manipulation to ensure it'll be
on top of @INC. For some reason lib has changed to add directories in
a different order than it did before. [Stas]

Re: mp1, mp2 on same server?

[Evaldas Imbrasas <ev...@imbrasas.com>]

> If I want to run mp1 and mp2 on the same web server, I'm guessing I'll
> need different perl trees. Is there anything I should be concerned with in
> a setup like this? Memory issues or anything of the sort?

I'm running both apache1.3/mp1 and apache2/mp2 on my development
sandbox. I use the same perl tree (system) for both. One thing to keep
in mind is that you want to install mp1 first, and mp2 afterwards. I
know people who tried installing it the other way round and had
problems, although I'm not sure exactly what kind, since I did it
right from the start.

I wouldn't use this kind of setup for a production enviroment, though.
Hardware is cheap, so splitting apache1.3/mp1 and apache2/mp2 to be
hosted on separate servers or server farms makes more sense.

--
-----------------------------------------------------
Evaldas Imbrasas
http://www.imbrasas.com

mp1, mp2 on same server?

[Diona Kidd <dk...@modernflow.com>]

Quick question. I hope this hasn't been asked a million times already.

If I want to run mp1 and mp2 on the same web server, I'm guessing I'll
need different perl trees. Is there anything I should be concerned with in
a setup like this? Memory issues or anything of the sort?

For instance,

apache 1.3
system perl
mod_perl 1.29

---------------

apache2.2
new perl 5.8.7 tree
mod_perl 2
libapreq2

Thanks,

Diona