Hello,<div><br></div><div>I am working with Maven, and find your question interesting, but the source base it supports </div><div>is java and so I have not dealt with these issues.</div><div><br></div><div>Sorry that I could not be of assistance.</div>
<div><br></div><div>Chris<br><br><div class="gmail_quote">2010/12/7 Nicholas Wehr <span dir="ltr"><<a href="mailto:pm@bionikchickens.com">pm@bionikchickens.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello everyone,<div><br></div><div>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:</div>
<div><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><div>What I'm looking at is either using local::lib or PREFIX & LIB w/ cpan. What do you think?</div>
</div><div><br></div><div>Thanks in advance,</div><div>-nicholas</div>
<br>_______________________________________________<br>
San-Diego-pm mailing list<br>
<a href="mailto:San-Diego-pm@pm.org">San-Diego-pm@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/san-diego-pm" target="_blank">http://mail.pm.org/mailman/listinfo/san-diego-pm</a><br></blockquote></div><br><br clear="all"><br>-- <br>Realisant mon espoir, je me lance vers la gloire.<br>
Christopher Hahn == <a href="mailto:xrz1138@gmail.com">xrz1138@gmail.com</a><br>
</div>