[sf-perl] [announce] Pinto-0.026
moseley at hank.org
Thu Dec 15 02:37:34 PST 2011
2011/12/8 Jeffrey Thalhammer <jeff at imaginative-software.com>
> So I invite you to kick the tires on Pinto<https://metacpan.org/release/THALJEF/Pinto-0.026> and
> give me your feedback. Beware that Pinto has a lot of dependencies, and
> I'm still not sure what the minimum versions should be. So I recommend
> brewing a fresh perl or using the -L option with cpanm(1) to install Pinto
> into a clean (and separate) sandbox. Pinto is still alpha code and subject
> to change in incompatible ways.
I'm trying to understand the big picture. Any primer or "getting started"
docs to help the impatient? Or maybe just a walk-through of typical
workflow? How could developers on different machines all access a single
"repo" of distributions?
My goal at this point is to have a private CPAN-style repo available on our
LAN where we can add our in-house modules and run "cpan Our::Module" and
have it automatically install from our local repo (or from CPAN, if it
I don't think we want to check out an "installed" Perl lib (say a copy of a
local::lib library) due to different architectures. We too often get
developers blocked due to some common module dependency issue using shared
libs -- I think developers with their own local::lib or even perlbrew is
the easiest way for everyone to get along on the same machine.
Frankly, I don't think it's that hard to svn checkout the module and
install it manually using local::lib, but some our of code has so many
in-house dependencies that it's somewhat of a pain to do that if some time
has passed since last working on the code. Plus, svn may have the module
in an unstable state and not "release" ready. Just running Makefile.PL &&
make on one of our apps to bringi in all the in-house dependencies would
make it much less painful. And make preparing RPMs for a release simpler,
moseley at hank.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SanFrancisco-pm