brucezepplin has asked for the wisdom of the Perl Monks concerning the following question:

I am trying to run the bioperl-live package and I have git-cloned the following repo

git clone https://github.com/bioperl/bioperl-live.git

and cd'd into bio-perl live where it was installed. I have then tried to run:

perl Build.PL

to which I get back:

Checking prerequisites... build_requires: ! Test::Most is not installed

so I have opened up a cpan shell and when i run from cpan:

cpan>install Test::Most

and repeat the build I get the same error. Would anyone mind cloning the above git repo ( found at https://github.com/bioperl/bioperl-live if you want to check yourself) and let me know if you are encountering the same problem. note this doesn't happen for other Build.PL files in other packages - it runs fine. there must be something in that git repo that's corrupt/missing.

Thanks update - when I run perl -wle 'use Test::Most' I get:
Can't locate Test/Most.pm in @INC (@INC contains: /home/arron/src/biop +erl-live /etc/perl /usr/local/lib/perl/5.12.4 /usr/local/share/perl/5 +.12.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.12 /usr/share/p +erl/5.12 /usr/local/lib/site_perl .) at -e line 1. BEGIN failed--compilation aborted at -e line 1.`enter code here`
Also configuring cpan to install as root and then installing Test::Most makes no difference. such a fuss!

Replies are listed 'Best First'.
Re: Build.PL wont run in git repo
by bioinformatics (Friar) on Apr 24, 2013 at 22:03 UTC

    What platform are you compiling for? I just tried compiling the latest from bioperl-live and Build.pm has been removed from Bio/Root. I know that CJ has been making a lot of changes to how the modules are organized. I would jump on the IRC channel to get help by the devs, frankly. Can you do with just the latest release, or do you need a specific patch?

    EDIT: Can you just export PERL5LIB=/path/to/bioperl-live:$PERL5LIB?

    Bioinformatics
Re: Build.PL wont run in git repo
by Anonymous Monk on Apr 25, 2013 at 03:25 UTC

    Well that is what happens with live/trunk, it isn't always in a runnable state

    check out the latest stable release and use that instead