Re^2: OpenBSD or FreeBSD for a Perl web app Production platform?

This is why I install my own perl in /usr/local/perl-x.x.x. I have code that I use here at work to use CPAN and install all the modules we need. Then I have a link /usr/local/perl which points to the production version. I like this setup since I can install a new version of perl and modules, have users test using the self contained install. When testing is done, I point /usr/local/perl to the new version directory. I let the ports that need perl install it and let portupgrade handle the updates.

Comment on Re^2: OpenBSD or FreeBSD for a Perl web app Production platform?

Replies are listed 'Best First'.

Re^3: OpenBSD or FreeBSD for a Perl web app Production platform?
by graff (Chancellor) on Sep 25, 2006 at 22:44 UTC

It makes life tolerable, but there are still traps for the unwary -- e.g. when scripts are copied in from other places that don't happen to share this subtle distinction in perl paths. Just another of those gritty details that users of perl scripts need to stumble over now and then...

We could also opt for "#!/usr/bin/env perl" as the shebag line, and control the relative ordering of /usr/local/bin and /usr/bin in PATH. But that's not exactly a comfortable solution either; it just passes the discomfort to the user's shell environment instead of the script maintainer's choice for the shebang line, which is probably a really bad idea.

[reply]


Syntactic Confectionery Delight
	PerlMonks