Re: Running Under Some Shell

Please correct, expand, and illuminate.

With regard to the big picture: you've spent time and brain to avoid your system's perl in a development environment, because you've been bitten by installs via cpan, and you want to achieve compatibility between your development and productive environments.

You've gone a long way (and learned much in the process, I bet.) Time to step back and meditate...

Why, Oh Why, don't you just package CPAN modules according to the requirements of the package manager of your OS, forget about cpan, use the perl shipped with your OS and put your wit into things that matter?

Comment on Re: Running Under Some Shell Select or Download Code

Replies are listed 'Best First'.
Re^2: Running Under Some Shell by Xiong (Hermit) on Feb 25, 2010 at 09:19 UTC
Why install a second `perl` with its own module library? I've learned much, which should be justification enough for any effort; nor do I think my education is finished. Primarily, I feel comfortable with this separation of church and state. I enjoy the rare feeling of actually going along with the majority opinion. I get to experiment freely, even rashly, with the development environment without fearing to wake up to funny green squiggles marching across my screen. There's a limit to this, I guess, but a develenviron pushes that limit a bit further away. Compiling locally is good preparation for building the production environment on remotehost. I have just about got comfortable with the idea of throwing out remotehost's `perl 5.8.8` entirely and installing fresh to match `localhost:/lab`, thereby blowing away the version compatibility questions, the module version questions, and the cargo cult module loader prescribed for lesser mortals. I've compiled my dev `perl` as `5.10.1`, which beats Ubuntu's default install of `5.10.0`; I've also now got threading and debugging support. I might could substitute my new, hot-rod `perl` for system use. It's also possible that I could try and end up with blue flames shooting from the vents. On the gripping hand, my nice clean Ubuntu system works; and my nice new dev `perl` works.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Running Under Some Shell
by Xiong (Hermit) on Feb 25, 2010 at 09:19 UTC

Why install a second perl with its own module library?

I've learned much, which should be justification enough for any effort; nor do I think my education is finished. Primarily, I feel comfortable with this separation of church and state. I enjoy the rare feeling of actually going along with the majority opinion.

I get to experiment freely, even rashly, with the development environment without fearing to wake up to funny green squiggles marching across my screen. There's a limit to this, I guess, but a develenviron pushes that limit a bit further away.

Compiling locally is good preparation for building the production environment on remotehost. I have just about got comfortable with the idea of throwing out remotehost's perl 5.8.8 entirely and installing fresh to match localhost:/lab, thereby blowing away the version compatibility questions, the module version questions, and the cargo cult module loader prescribed for lesser mortals.

I've compiled my dev perl as 5.10.1, which beats Ubuntu's default install of 5.10.0; I've also now got threading and debugging support. I might could substitute my new, hot-rod perl for system use. It's also possible that I could try and end up with blue flames shooting from the vents.

On the gripping hand, my nice clean Ubuntu system works; and my nice new dev perl works.

[reply]
[d/l]
[select]