Development of Perl's Module::Build ()

John Peacock | 14 Mar 2010 03:24

Re: Releasing a candidate

On 03/13/2010 07:26 AM, Johan Vromans wrote:
> Working late to get a release candidate ready for upload.
> Change the version number to "2.00.RC1". Yes, with quotes.

Where?  Did you change that in Build.PL or in the $VERSION assignment in 
the main .pm file?

> Version '2.00.' ?
>
> Did I miss something in the docs about not being able to manifacture
> your own version number?
            ^^^^^^^^^^^^^^

Version number is the applicable phrase there.  Perl doesn't understand 
anything except numbers (and PAUSE/CPAN too as far as I know).  You 
/could/ use version::AlphaBeta (but I wouldn't recommend it).  This 
doesn't really have anything to do with version.pm, per se, but that 
won't help matters (since the parser will explicitly stop at the first 
non-numeric).  Try running `perl -w Build.PL` and see what that tells you.

You cannot just dump random text into $VERSION and expect it to work. 
Among other things, how do you expect tools to sort this release with 
all of the other releases you are making?

John

headers

Johan Vromans | 14 Mar 2010 14:21

Re: Releasing a candidate

[Quoting John Peacock, on March 13 2010, 21:24, in "Re: Releasing a cand"]
> Where?  Did you change that in Build.PL or in the $VERSION assignment in 
> the main .pm file?

In the main .pm file.
I did work around the problem by adding an explicit dist_version to
Build.PL. 

> You cannot just dump random text into $VERSION and expect it to work. 
> Among other things, how do you expect tools to sort this release with 
> all of the other releases you are making?

print "yes" if "2.00 RC1"  lt "2.00.00";
print "yes" if "2.00(RC1)" lt "2.00.00";

What would your suggestion be to distinctively denote a release
candidate? 

-- Johan