<HTML>
<HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2"><b>On Tue, 7 Dec 2010 15:46:35 -0800, Nicholas Wehr wrote</b>
<br />> Hello
everyone,
<br />>
<br />> First off, beware, I'm a bit nutty when it comes
to configuration management. I've recently deployed a Hudson instance and
wanted to move some Catalyst projects into it. What I'd like to solicit
feedback on here is: <i>how are you managing your Perl dependencies in these
build systems? </i>Here's some goals I
have:
<br />>
<ul>
<li>do not assume any non-core modules are installed on the build
platform</li>
<li>use specific version of modules in the built product - product
is a Catalyst website for example (@inc or use lib)</li>
<li>need to archive
specific version of CPAN dependencies offline; this means we can recreate a
product without an internet
connection</li>
<li>allow for the rebuild of dependencies when the build platform has changed;
this is meant to address a platform change from 32bit to 64bit</li>
</ul>
<br />>
What I'm looking at is either using local::lib or PREFIX & LIB w/ cpan.
What do you
think?
<br />
<br />Hi Nicholas,
<br />
<br />On my personal projects I adhere to the Linux Filesystem Hierarchy Standard [0], modules go to /usr/local/ and lib search includes that path location as first option.
<br />
<br />Regards,
<br />
<br />
<br />[0] http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
<br />
<br />--
<br />
Urivan Flores-Saaib
<br />
saaib@ciberlinux.net
<br />
(858)
431-9734
<br />
</font>
</BODY>
</HTML>