Marc wrote:
Shawn,
if you use perlbrew and local::lib you
can test different perl versions and then different environments.
I haven't looked into local::lib yet. What advantage does that give
you over a plain perlbrew install?
Marc
I haven't used local::lib very much, because perlbrew seems to be the
easiest catch-all solution for my purposes. Once I discovered the
"--as" installation parameter (e.g. "perlbrew install 5.14.1 --as
perl514_sandbox2", etc.), I had very little use for local::lib. Since
perlbrew sets @INC to line up with the "--as" in each installation, one
can create multiple isolated installations of the same Perl version. In
my (limited) experience, cpan worked correctly under whichever
installation was marked active with "perlbrew use" (or "switch").
The downside of this approach is that I'm compiling the same version of
Perl multiple times, for the sole purpose of different installation
directories. That takes time and hard drive space. So I can see how
local::lib may be better if those are critical issues. But for me,
adding another ~70MB copy of Perl to my home directory is
inconsequential when weighed against the ease of using one tool to do
the job. Each to their own.
Besides saved disk space and install time, I'd be interested in knowing
if I've overlooked some other advantage of local::lib over perlbrew.
Brian
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
