This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: Exceptions section dropped? From: Stas Bekman <stas@stason.org> Date: Mon, 14 Aug 2000 13:04:45 +0200 (CEST) Hi, Andreas > >>>>> On Mon, 14 Aug 2000 10:04:33 +0200 (CEST), Stas Bekman <stas@stason.org> said: > > cpan> install mod_perl_guide > > Running make for S/ST/STAS/Apache-mod_perl_guide-1.22.tar.gz > > > Got another SIGINT > cpan> install Apache::mod_perl_guide > > Running make for S/ST/STAS/Apache-mod_perl_guide-1.23.tar.gz > > > ...while the latest version is 1.25. Something is wrong. > > > I won't delete the previous versions of the Guide now, so whoever handles > > CPAN now (I think it's Jarkko Hietaniemi) will be able to verify and debug > > this apparently broken behavior. > > If you want to use CPAN.pm as a distribution medium for the guide, you > need to be careful about versioning. You need to tell people which > module (or pseudo module) they should install in order to get the > guide and you should then make sure that this module always carries > the latest version number. > > You need to know that PAUSE is parsing the *.pm files in order ot > guess the $VERSION. I do know that. > So when I look at 1.25, I find only one file that contains the > $VERSION=1.25 and that is src/Version.pm. And that file does not have > a package declaration, so PAUSE has no chance to guess which package > is referred to. That's my fault. I was confused by Makefile.PL's: VERSION_FROM => 'src/Version.pm', > Note that PAUSE is parsing, not interpreting the code, so perl tricks > do not work. You need to write pretty straightforward code. Ok > So, I hear you asking, "what should I do"? I believe that you should > include the $VERSION=1.25 in your mod_perl_guide.pm where there is > already a package declaration. If it doesn't work, let me know shortly > after the upload, and I'll find a better suggestion. I know what should I do: src/Version.pm: package Apache::mod_perl_guide; $VERSION = '1.26'; 1; Does this look good? At this point I'll solve it by removing the old versions from CPAN. And starting from the next release this should be clean. ===