Module dependencies and packages

David Miller justdave at
Wed May 16 19:00:45 UTC 2007

Aaron Trevena wrote on 5/16/07 11:39 AM:
> On 16/05/07, Teemu Mannermaa <wicked at> 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.

Or roll your own RPMs.  I tend to do that a lot.  Most of the time
building an RPM is pretty easy.  And when you're running a couple
hundred servers, it's a lifesaver to have a list of what the installed
packages were to restore to a new machine with the data backups if a
hard drive takes a nose-dive.

Dave Miller                         
System Administrator, Mozilla Corporation
Project Leader, Bugzilla Bug Tracking System

More information about the developers mailing list