On Wed, Jun 01, 2011 at 10:51:41AM +0200, Steffen Schwigon wrote:
> I used CPAN::Mini a lot but now start using *real* CPAN mirrors for
> the distroprefs mechanism that CPAN.pm provides (needed to work around
> any known problem on CPAN).
You can, of course, use distroprefs with any CPAN-like mirr
Hi,
On Wed, Jun 1, 2011 at 9:51 AM, Steffen Schwigon wrote:
> I *think* (but haven't tried yet) that combining both might be good:
>
> - a local real CPAN mirror for the latest full CPAN
> - an additional CPAN::Mini (plus ::Inject) to add your own lcoal
> modules
>
> AFARI CPAN.pm looks into
Jeffrey Thalhammer writes:
> [build private CPANs]
Just to add an experience for completeness of this discussion:
I once tried to snapshot a complete MINICPAN with git every time I
verified a CPAN::Mini sync with my application's “cpan upgrade ; make
test”.
But it did not work out well due to
Jeffrey Thalhammer writes:
> Now this is where it gets interesting. Rather than install in
> site_perl, it installs into a directory right inside my project
> (let's call it "dlib" for "dependent libraries"). At the same time,
> it stashes the tar balls in a directory structure suitable for a
>
David Cantrell writes:
> FWIW, my solution (which I haven't tried) would be:
>
> * make an up-to-date mirror of the most recent versions of everything on
> the CPAN, using CPAN::Mini;
> * use CPAN::Mini::Inject to add your own modules to the mirror.
I used CPAN::Mini a lot but now start using *
