develooper Front page | perl.module.build | Postings from April 2007

New M::B version and bleadperl integration

Thread Next
From:
John Peacock
Date:
April 23, 2007 13:44
Subject:
New M::B version and bleadperl integration
Message ID:
462D1ACD.8090309@rowman.com
Against my better judgement, version-0.7203 produces slightly different
stringification results for version objects, which in turn produces two test
failures with Module::Build 0.2807.  This only shows up when version.pm is
installed before Module::Build is updated.

I would strongly recommend releasing a new point release for Module::Build with
the updated version code, so that unnecessary test failures won't be a nuisance
for other modules.  I'm sorry that I didn't forsee these problems and make this
recommendation before releasing the latest version.pm code to CPAN...

At the same time, while integrating the latest version.pm code into bleadperl,
it became obvious that the Module::Build::Version class in bleadperl should no
longer include the self-contained version.pm code.  Rather than changing the
core Module::Build code to call version->new() instead of
Module::Build::Version->new(), it make more sense to leave the M::B::V module as
is, but eliminate all of the duplicated version code.  Essentially, all that is
required is:

> package Module::Build::Version;
> use strict;
> 
> use vars qw($VERSION);
> $VERSION = 0.7203;
> use base qw/version/;

If you are OK with this, I will keep this module in sync with the underlying
version.pm $VERSION, if I should release any further updates to bleadperl.  That
way, you don't need to maintain two releases (once for CPAN and once for blead).

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Blvd
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About