From simon at technocool.net  Thu Nov  6 05:05:49 2008
From: simon at technocool.net (Simon Waters)
Date: Thu, 06 Nov 2008 13:05:49 +0000
Subject: [DCPM] autobundle gotchas?
Message-ID: <4912EBAD.3080203@technocool.net>

Looking to bring a server into line with a test server in terms of 
modules and versions.

This server had a rather mangled version of CPAN, which is now upgraded 
to something shiny and new, so it now says a lot of modules could be 
upgraded.

Having tried autobundle on a few test package, between two test 
machines, it seems to do mostly sensible things.

Since the test box is shiny and relatively up to date as far as Perl 
modules go I think this should be straight forward. But I'm open to 
being told of the dark side of autobundle before I try it.

Why isn't autobundle the "FAQ" answer for finding locally installed 
modules instead of the apparently near useless "perldoc perllocal" or is 
the frequently asked question the wrong question? perllocal is great for 
saying what happened, but useless from an administration perspective 
when you go from a few modules to hundred or thousands when you need to 
automate these things.

Any tips on minmising the noise from questions appreciated as well...

  Simon still messing with pre-5.10 stuff.







From simon at technocool.net  Thu Nov 13 13:31:30 2008
From: simon at technocool.net (Simon Waters)
Date: Thu, 13 Nov 2008 21:31:30 +0000
Subject: [DCPM] autobundle gotchas?
In-Reply-To: <4912EBAD.3080203@technocool.net>
References: <4912EBAD.3080203@technocool.net>
Message-ID: <491C9CB2.2080406@technocool.net>

Simon Waters wrote:
> 
> Since the test box is shiny and relatively up to date as far as Perl
> modules go I think this should be straight forward. But I'm open to
> being told of the dark side of autobundle before I try it.

Dark side is mostly it is verbose, slow, and doesn't order the list by
dependency status. I'm sure these are fixable, and may be with 5.10 and
CPANPLUS there is a better way....

There is also the insanity of the variation in building between modules
- more Gentoo than Debian goodness this CPAN stuff. At least two module
tests appeared to hang indefinitely (the control key is there for a
purpose).

We were only aware of one module that changed it's interface in a
non-backward compatible way (JSON), and we'd coded around that before
updating.

I probably should just turn all the modules into Debian packages, but
that requires me to learn stuff as well as working hard....