Re: Where to unpack CPAN modules

Sounds like you want your own development environment. I recommend compiling your own perl for that and giving it a prefix for installation. Personally I have everything in ~/installed/ with my path including ~/installed/bin. This lets me install perl cleanly and use it without disruption to the rest of the system (Debian makes heavy use of perl). Then when I run the cpan shell it pulls all its location stuff from Config.pm which conveniently points everything to ~/installed/. Inside of ~/installed, I keep a cpan directory and let CPAN use that as it's scratch space. All in all, it works well.

Comment on Re: Where to unpack CPAN modules Select or Download Code

Replies are listed 'Best First'.
Re^2: Where to unpack CPAN modules by tphyahoo (Vicar) on Dec 16, 2006 at 15:19 UTC
Second that. I recently google-project-hosted a collection of bash scripts that I use to automate setting up my own local perl environment wherever I want. Pedantically thorough one-shot catalyst sandbox installation, soon it will automagically set up demo apps too... This is optimized for catalyst development, but if you edit install.sh and remove all the stuff related to catalyst, you should have an easy way to set up perl, update CPAN, add Module::Build. And maybe the tactics I use in terms of overly thorough backup of my environment, with easy aliases to help you on your way, could be of use as well.	[reply]

Replies are listed 'Best First'.

Re^2: Where to unpack CPAN modules
by tphyahoo (Vicar) on Dec 16, 2006 at 15:19 UTC

Pedantically thorough one-shot catalyst sandbox installation, soon it will automagically set up demo apps too...

This is optimized for catalyst development, but if you edit install.sh and remove all the stuff related to catalyst, you should have an easy way to set up perl, update CPAN, add Module::Build. And maybe the tactics I use in terms of overly thorough backup of my environment, with easy aliases to help you on your way, could be of use as well.

[reply]