Module dependencies and packages

[Aaron Trevena]

On 16/05/07, Teemu Mannermaa <wicked at etlicon.fi> wrote:
> > just plain broken or configured by crack monkeys, or can clash with
> > cpan modules so you have multiple versions, etc (I don't think this is
>
> Yes, that's why it's never a good idea to use CPAN on systems with
> package management. Probably one of the important rules about package
> management is that you never ever should install anything without
> telling it to your package manager. Having unknown, unlisted files is a
> sure way to get you into trouble with package manager.

I'd go the other way around personally - anything that is critical to
development means not relying on some distro maintainers to keep up to
date - for serious systems it's better to use your own perl and CPAN.

cpan and cpanplus are both package managers, they just do Perl rather
than everything :)

Also freebsd package management plays nice with CPAN - it's debian and
redhat that are breaking things.

> > right software - you can bundle dependancies along with the package
> > and only install them if they aren't already installed or are newer
>
> For our Tinderbox installation that runs our automated test suite (the
> files under t/ subdirect) I ended up building special RPM files that
> contain different versions of supported Perl interpreters and required
> Perl modules. It wasn't that bad but making all those modules to build
> and especially making their tests pass was getting hard. :(

Of course you can just use PAR. In fact using PAR and bundling it in
with Bugzilla would make deployment a lot easier and simpler for new
users.

A.

-- 
http://www.aarontrevena.co.uk
LAMP System Integration, Development and Hosting