George Hartzell | 23 Sep 23:13
Gravatar

confused about version numbers.


I recently realized that I needed a feature from
Bio::Search::Hit::GenericHit that exists in the svn trunk but isn't in
the CPAN's version bioperl-1.5.2_102.

I thought I'd just specify a version number in my Build.PL and that
way I could sleep soundly.

But, it looks like $Version in CPAN's Bio::Root::Version is
1.005002_102 while in the trunk it's 1.005002_100.

What's the proper way for a Build.PL to be sure that it has a current
bioperl?

g.
Steve Chervitz | 24 Sep 00:05
Gravatar

Re: confused about version numbers.

Here's the general recommendation from the FAQ:

http://bio.perl.org/wiki/FAQ#How_can_I_tell_what_version_of_BioPerl_is_installed.3F

Not sure the recommended way to do this from a Build.PL. You could so such
checking within a BEGIN block in your Build.PL, perhaps.

Steve

On Tue, Sep 23, 2008 at 2:16 PM, George Hartzell <hartzell <at> alerce.com>wrote:

>
> I recently realized that I needed a feature from
> Bio::Search::Hit::GenericHit that exists in the svn trunk but isn't in
> the CPAN's version bioperl-1.5.2_102.
>
> I thought I'd just specify a version number in my Build.PL and that
> way I could sleep soundly.
>
> But, it looks like $Version in CPAN's Bio::Root::Version is
> 1.005002_102 while in the trunk it's 1.005002_100.
>
> What's the proper way for a Build.PL to be sure that it has a current
> bioperl?
>
> g.
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l <at> lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-l
(Continue reading)

Sendu Bala | 23 Sep 23:51
Favicon

Re: confused about version numbers.

George Hartzell wrote:
> I recently realized that I needed a feature from
> Bio::Search::Hit::GenericHit that exists in the svn trunk but isn't in
> the CPAN's version bioperl-1.5.2_102.
> 
> I thought I'd just specify a version number in my Build.PL and that
> way I could sleep soundly.
> 
> But, it looks like $Version in CPAN's Bio::Root::Version is
> 1.005002_102 while in the trunk it's 1.005002_100.

Fixed. It's now 1.005002_103.

> What's the proper way for a Build.PL to be sure that it has a current
> bioperl?

Your method was sound, I think.

Gmane