David Golden wrote:
On 10/31/06, Gabor Szabo <[EMAIL PROTECTED]> wrote:
In a way this is what Linux distros do or ActiveState does, but I
would like to do it
on CPAN level and still in source code.
As a start I could possibly creat a minicpan for particular modules
and their cross-tested
versions.
Does this make sense?
It does. I was asked about something like this for use at work by
someone at Perl Seminar NY and my answer was that he should look into
CPAN::Mini and CPAN::Mini::Inject.
Perhaps you should consider writing a CPAN::Mini extension that makes
it easy to create and maintain a minicpan repository with the features
that you want. Rather than mirroring just CPAN, I would imagine it
would probably draw from Backpan as well. Given a list of modules and
optional versions, get either the latest module from CPAN or a
specific module from BackPAN. Call it CPAN::Mini::Subset or
something.
(I also just looked at CPAN and noted CPAN::Mini::Tested and
CPAN::Mini::Phalanx100 as variations of this kind of thing.)
Rather than try to hack this kind of thing into the toolchain, I'd
suggest just making it easy to create and maintain custom
repositories.
At times, I've seen people suggest there needs to be a "recommended"
list for CPAN modules to get past the 1000 or so Class modules, the
100 or so Getopt modules and so on. If it was easy to create custom
repositories, then those who wanted to could create their custom
minicpans of recommended modules and publish them to the world.
(Then someone can go write CPAN::Mini::Superset to create a minicpan
that merges other minicpan repositories.)
I was heading in that direction with CPAN::Index and the various other
distribution modules I released over the last month.
Anyone who wanted to look into this might like to start with those...
Adam K
