[Bioperl-l] Splits again
hlapp at gmx.net
Sat Jun 30 17:26:22 EDT 2007
On Jun 28, 2007, at 3:19 PM, Sendu Bala wrote:
> Very definitely the latter. The key benefit of my approach is that
> the organisation stays as is and that a snapshot of the repository
> remains a single directory of modules in Bio so that people don't
> have to 'install' Bioperl, they can still just uncompress the
> archive (or check out the package from svn) and point their
> PERL5LIB to the root dir of the package.
I think this is absolutely key to keep in mind. Anything without this
feature will likely be a non-starter.
I don't really have time to follow the discussion let alone
participate, so really all I can contribute is to offer some sanity/
reality checks (such as the above).
In this sense, I understand a release pumpkin will generate ~900
packages to upload to CPAN? How much hassle is that compared to what
uploading a bioperl release means right now?
How brittle is all the Build.PL code that will be needed to automate
all of this, and how difficult will it be to maintain? For example,
if someone adds in 10 new modules, what Build.PL-related work will
need to be done?
: Hilmar Lapp -:- Durham, NC -:- hlapp at gmx dot net :
More information about the Bioperl-l