On Sep 1, 4:54 am, byu...@langly.dyndns.org ("Brian F. Yulga") wrote:
> 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

That basically summarizes why I put the feature request for perlbrew
forward, so that it could encapsulate the usefulness of local::lib
within perlbrew. You shouldn't need to keep installing and compiling
perls.

rvm if you haven't tried it really works well(for ruby).
https://rvm.beginrescueend.com/rvm/

Here is a direct knock off of perlbrew called pythonbrew
https://github.com/utahta/pythonbrew#readme
Essentially all the commands are the same

such as
pythonbrew install 2.7.2
pythonbrew switch 2.7.2

It has implemented a few nice features.

Runs a named python file against specified and/or all pythons:
pythonbrew py -p 2.7.2 -p 3.2 test.py # Use the specified pythons

and then there virtual implementation.

Create isolated python environments (uses virtualenv):
pythonbrew venv init
pythonbrew venv create proj
pythonbrew venv list
pythonbrew venv use proj
pythonbrew venv delete proj

Cheers

Sayth


--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/


Reply via email to