stas at stason
Jan 26, 2006, 2:15 PM
Post #2 of 2
(1678 views)
Permalink
|
|
Re: issues with figuring out which mp version is running
[In reply to]
|
|
Frank Wiles wrote:
> On Mon, 23 Jan 2006 16:05:57 -0600
> Frank Wiles <frank [at] wiles> wrote:
>
>
>> I'll also update the docs to reflect this as there are a couple
>> of places this needs to change.
>
>
> Here is a patch to update the docs to get rid of the use of
> $mod_perl::VERSION in the 2.0 docs. I've basically replaced
> any use of:
>
> use constant MP2 => ($mod_perl::VERSION >= 1.99);
>
> or the similar constructs with:
>
> use constant MP2 => ( exists $ENV{MOD_PERL_API_VERSION} and
> $ENV{MOD_PERL_API_VERSION} >= 2 );
>
> I also removed a paragraph about how you need to make sure your
> module's $VERSION appears before using $mod_perl::VERSION in the code
> otherwise CPAN freaks out. I removed it because it no longer made
> sense to have it there, since it wasn't talking about
> $mod_perl::VERSION any longer.
Thanks Frank, committed.
--
_____________________________________________________________
Stas Bekman mailto:stas [at] stason http://stason.org/
MailChannels: Assured Messaging(TM) http://mailchannels.com/
The "Practical mod_perl" book http://modperlbook.org/
http://perl.apache.org/ http://perl.org/ http://logilune.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe [at] perl
For additional commands, e-mail: docs-dev-help [at] perl
|
mp_api_version.patch
