Re: Advice on Splitting Large Distributions in CPAN

By all means, use bundles. Here's a bundle that I put together for a "basic bioperl":

#!/usr/bin/perl

use strict;
use warnings;
use CPAN;

our $FORCE;

CPAN::Shell->force('install',

"Bundle::BioPerl",
"Bio::Seq",
"Bio::SeqIO::staden::read",
"Bio::Factory::EMBOSS",
"Bio::Tk::SeqCanvas",
"Bio::DB::Annotation");
[download]

This covers a lot of ground, but it's enough to get up and running with bioperl.

Comment on Re: Advice on Splitting Large Distributions in CPAN Download Code

Replies are listed 'Best First'.
Re^2: Advice on Splitting Large Distributions in CPAN by nathanhaigh (Initiate) on Jul 23, 2008 at 01:13 UTC
I think you misunderstand. Bioperl consists of 10's in not hundreds of modules, as new modules are developed they are simply added to the growing list of modules available under a single CPAN package. This makes it difficult for a third party to reuse Bioperl code in their own scripts/applications as it would require the whole Bioperl package to be installed as a prerequisite. Therefore the devs are looking to split up Bioperl into smaller chunks with dependencies correctly setup between these smaller chunks. Therefore if someone wants to be able to read/write sequence files from their own script, they will then only need to depend on a smaller subset of the Bioperl modules i.e. Bio::SeqIO::* The question is, how small can these chunks be? Is there any limitation or is it simply a maintainence issue for the devs if they split things up too much? After the split, several bundles could be made to organise the smaller subsets of modules into larger bundles with similar functions.	[reply]
Re^3: Advice on Splitting Large Distributions in CPAN by tilly (Archbishop) on Jul 23, 2008 at 02:56 UTC
There is no limitation. It is all a maintenance issue. However if the cross-dependencies mean that a group of modules is realistically always installed together, then there is absolutely no real benefit to splitting them.	[reply]