On Sun, Apr 12, 2009 at 11:20 PM, Eric Wilhelm <enoba...@gmail.com> wrote: > # from Joshua ben Jore > # on Sunday 12 April 2009 20:06: > >>> http://www.perlfoundation.org/perl5/index.cgi?perl_best_admin_practices >> >>It may be a best practice to maintain your own perl but having just >>done this at work, it's a massive time sink. Our new platform at work >>is an Ubuntu mod_perl system with 208 CPAN modules. We produced a .deb >>for perl+modules and another for mod_perl > > Only *one* .deb for perl and all of the modules?
Yes. One deb. We've whittered about making more individual .debs but it's so annoying to create them that I think we'll likely not change. We don't go through this effort for Ruby+gems because currently we think we can apt-get install it and gem install the rest without conflicting since we deem it unlikely anything on the current system actually cares super-hard about it. >>but it took us several weeks >>to do it and we had to learn a bunch about how to author for Debian. >>It was painful and I don't recommend it for most people. > > You don't have to do it as Debian packages. Simply installing from > source and then building a full set of modules has never taken me more > than a few hours. /Now/ I can rebuild the set inside of half an hour which is /actually/ about 28 minutes too long. More highly annoying things are CPAN.pm being unable to install from a set of local tarballs. I tried for a bit to manufacture some small bits of program to create a local CPAN repo and had some success but not enough that my sysadmin incorporated it. If I figure out a recipe that works nicely, I'll share it. Josh
