Re: Using RPMs to package and install your own perl libs

[tomfahle]

Well, it ain't that easy.

Dave Cross gave a talk at YAPC::Europe 2008 "Perl in RPM-Land" and launched a project to automatically build RPMs from all modules uploaded to CPAN.

Fedora offers some help on Packaging:Perl and cpanspec

Hth,
Thomas

[zerohero]

OK, after looking at this information, it seems like the much saner thing would be to adhere to the CPAN standard for packaging (e.g. using Module::Starter), and then do a local cpaninject, and use cpan to deploy all my (local) perl packages. This has the slight downside that perl will be "an end in itself". But then again, I'm not going to use perl as base libraries for other programs (e.g. GUI apps).

The basic issue seems to be mixing packaging systems, and the usual problems having two standards causes. Note, however, that there have been people doing auto RPM builds as early as 2003. I stumbled upon this guy's site...http://rpmpan.sourceforge.net/, in addition to the ref you gave.

[tomfahle]

I'd like to recommend Perl Best Admin Practices over at Perl 5 Wiki:

• Build it yourself
• Leave the system Perl alone
• Isolate your perl installs so you can have many installed in parallel
• Keep up to date
• Use CPAN modules

Cheers,
Thomas

[gsiems]

I just set up cpanspec on my CentOS4 box to give it a spin.

Although getting it setup was slightly annoying (not all the dependencies are available without going to EPEL, etc. or to CPAN), however it appears to work very nicely.

++ and thanks for the tip.