installing a lot of perl modules
Hi List, Does anybody have recommendations for installing a bunch of perl modules that aren't in RPM? We have a few that require some custom compile settings. Currently, I'm doing a painful process of installing on a clean machine, compiling and installing, then making a tar ball from the output of "make install". Then during post-install, copying and un-tarring them onto the new system. This gets us by for now, but is horribly non-maintainable for future upgrades. What's the "best practice" for installing custom-compiled perl modules, or modules that are not pre-packaged in RPM's. Thanks! -- Ryan
output of "make install". Then during post-install, copying and un-tarring them onto the new system.
Why don't you do this with the modules and then compile them into the new system ? for instance during the first boot with a rc script ? You gain time for the creation of the cdrom (you juste have to copy modules on a directory on the cdrom) but however you loose time if you've got a lot of systems to install !
Op donderdag 24 februari 2005 23:50, schreef Ryan Allen:
Does anybody have recommendations for installing a bunch of perl modules that aren't in RPM? We have a few that require some custom compile settings. Currently, I'm doing a painful process of installing on a clean machine, compiling and installing, then making a tar ball from the output of "make install". Then during post-install, copying and un-tarring them onto the new system.
Use cpan2rpm, there are rpms available in the apt repository, in the directories: suser-sbarnin and suser-oc2pus. The latter contains the most recent. ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.2-i386 -- Richard Bos Without a home the journey is endless
participants (3)
-
Pierre Allix -
Richard Bos -
Ryan Allen