[Bioperl-l] Next BioPerl release
Fields, Christopher J
cjfields at illinois.edu
Wed Feb 6 19:54:58 UTC 2013
On Feb 6, 2013, at 1:36 PM, Siddhartha Basu <sidd.basu at gmail.com>
wrote:
> Hi,
>
> On Tue, 05 Feb 2013, Fields, Christopher J wrote:
>
>> All,
>>
>> I am scheduling the next BioPerl CPAN release tentatively for March 1. Any help in triaging bug reports would be greatly appreciated!
>>
>> Amongst all other changes, as mentioned in a separate thread we will remove Bio::FeatureIO, now developed in a separate repository:
>>
>> https://github.com/bioperl/Bio-FeatureIO
>>
>> Feedback, suggestions, etc are greatly appreciated.
>
> Here are CI build report on 5.12, 5.14 and 5.16 using travis.
> https://api.travis-ci.org/jobs/4623997/log.txt?deansi=true
> https://api.travis-ci.org/jobs/4623998/log.txt?deansi=true
> https://api.travis-ci.org/jobs/4623999/log.txt?deansi=true
>
> Could not get 5.10 to work on travis. Though i activated the (--network)
> option, it still didn't run one of the test that needs network. Also, initially got
> confused by the fact that though it has dist.ini, the tests still has
> to run through Build.PL. Running **dzil test** do not work.
>
> Hope this helps.
>
> thanks,
> -siddhartha
Just to point out, that was for Bio-FeatureIO. Truthfully I'm not worried about that one yet; got to get over Mt. Everest first (the main release).
Build.PL is there mainly as a convenience for users w/o Dist::Zilla, which, last I recall, had a higher dependency list than even BioPerl (though I may be mistaken). I'll probably have to set up a Build.PL that can be clobbered by Dist::Zilla as needed. Or we can just get rid of it and insist that dev. code has to be added via 'use lib' or PERL5LIB, and not allow installation.
chris
More information about the Bioperl-l
mailing list