stas 2003/06/10 16:58:19
Modified: src/docs/2.0/user/porting porting.pod
Log:
add a note that module's own $VERSION must come first
Submitted by: Shannon Eric Peevey <[EMAIL PROTECTED]>
Revision Changes Path
1.7 +15 -0 modperl-docs/src/docs/2.0/user/porting/porting.pod
Index: porting.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/porting/porting.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- porting.pod 10 Jun 2003 23:47:28 -0000 1.6
+++ porting.pod 10 Jun 2003 23:58:19 -0000 1.7
@@ -1251,6 +1251,19 @@
my $fh = MP2 ? Symbol::gensym : Apache->gensym;
open $fh, $file or die "Can't open $file: $!";
+Though, make sure that you don't use C<$mod_perl::VERSION> string
+anywhere in the code before you have declared your module's own
+C<$VERSION>, since PAUSE will pick the wrong version when you submit
+the module on CPAN. It requires that module's C<$VERSION> will be
+declared first. You can verify whether it'll pick the I<Foo.pm>'s
+version correctly, by running this code:
+
+ % perl -MExtUtils::MakeMaker -le 'print MM->parse_version(shift)' Foo.pm
+
+There is more information about this issue here:
+http://pause.perl.org/pause/query?ACTION=pause_04about#conventions
+
+
Here's another way to find out the mod_perl version. In the server
configuration file you can use a special configuration "define" symbol
C<MODPERL2>, which is magically enabled internally, as if the server
@@ -1285,6 +1298,8 @@
L<mod_perl 1.0 and 2.0 Constants
Coexistence|docs::2.0::user::compat/mod_perl_1_0_and_2_0_Constants_Coexistence>
=back
+
+
=head1 Maintainers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
