<br><br><div class="gmail_quote">2011/12/8 Jeffrey Thalhammer <span dir="ltr"><<a href="mailto:jeff@imaginative-software.com">jeff@imaginative-software.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div>Hi everyone-</div><div><br></div><div>A few months ago, I was tasked with building a private CPAN for a new client. I had already done this a couple times before using CPAN::Site or CPAN::Mini, but I was never really happy with the results. So this time, I started from scratch. The result is called <a href="https://metacpan.org/release/THALJEF/Pinto-0.026" target="_blank">Pinto</a>, and it is now available on CPAN. Pinto is inspired by CPAN::Mini, CPAN::Mini::Inject, and OrePAN, but adds several interesting features (listed below).</div>
</div></blockquote><div><br></div><div>Good timing. I was just about to post a question asking how people manage their in-house modules. So, I'll take a look at this soon as I have some time.</div><div><br></div><div>
What I'm interested in is how others in an environment that includes a dozen or so developers manage their in-house modules. Most of our developers work on just a few "dev" boxes and currently (mostly) using a shared Perl library. I think either perlbrew or local::lib is the best solution for individual developers, but we also have a number of in-house modules in svn that our apps depend on. It would be very handy to have a local CPAN so that checking out an app and running "make" would bring in in-house dependencies just as if they were on CPAN.</div>
<div><br></div><div>Currently, some developers just check-out from svn the in-house module they need and install in local::lib, but mostly they get installed system-wide, which isn't a great approach.</div><div><br></div>
<div>Can anyone offer comments on how this is done in your organization?</div><div><br></div><div> </div></div><div><br></div>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org" target="_blank">moseley@hank.org</a><br>