On Fri, Sep 30, 2011 at 10:00 AM, Joe Landman < land...@scalableinformatics.com> wrote:
> For years, we've been putting our Perl under the > > /opt/scalable/ > > tree. We've run into so many problems with system supplied Perl, that in > general, we simply ignore it. We also have, in the past when we were doing > more Catalyst apps, shipped our baseline tree with everything pre-installed > ... it was *much* easier than going through a build > This is basically what we've been doing at $work, as well -- install our own Perl into /opt/perl (or something like that) with all the dependencies for our applications, pack it into an RPM, then deploy that to our customers' servers. Another thing that hasn't been pointed out is that the system Perl tends to be built in the most pants-on-head moronic way possible. Red Hat, in particular, enables ithreads, which almost nobody uses anymore (due to its faulty design) but incurs a severe performance penalty just for having it compiled in. Anyone that is serious about Perl development should probably be avoiding these builds like the plague. -- Stephen Clouse <stephenclo...@gmail.com>
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
