New RPMs for perl modules

godoy on 2002-06-21T14:20:27

I've packaged some stuff lately. They are already available in Conectiva's snapshot.

perl-Curses

perl-Error

perl-Filter

perl-IO-Tty

perl-Jcode

perl-Lingua-Ispell

perl-Log-Dispatch

perl-Log-Dispatch-Config

perl-POE

perl-POE-Component-IRC

perl-POE-Component-Logger

The decision criteria for which modules to package was: I need it to put my bot up. The logging modules entered because Matts asked for his POE module to be packaged too.

packaged modules

jdporter on 2002-06-21T18:38:11

What are those packages for?

I'm kinda curious, being the author of Lingua::Ispell.

Re:packaged modules

godoy on 2002-06-21T19:22:46
My intent with then was having them running here to use my bot. :-)

The RPMs were sent to Conectiva for distribution with their Linux version. It's easier to maintain RPM packages then perl modules. Specially when upgrading or migrating servers.

With RPM all you have to do is to reinstall the same packages (or let the application's dependencies require them). With Perl you'd need to loop through all your possible used directories searching for packages. If you are the only user of the machine, that's easy and you probably have all your modules under /usr/lib/perl5 or something like that. If you're on a shared machine, that's not that easy and users may have modules in their $HOME.

Though RPM is bad in some aspects, it's very good at this one. Maintaining a server using some kind of package management (RPM, DEB, etc.) is much easier that having to figure out what is installed and what version does it have.