Providing Perl on a shared web server
mkpm-20051014 at djce.org.uk
Sun Jan 22 04:54:36 PST 2006
On Fri, Jan 20, 2006 at 04:24:37PM +0000, Nik Clayton wrote:
> A related solution -- are you providing shell accounts for your users? If
> so, you could build a custom version of Perl that's configured to install
> modules in $HOME/lib, and to look for non-core modules in $HOME/lib too.
> Then it's your user's responsibility to install whatever modules they need.
> You take the disk space hit if multiple users all install the same module,
> but disk space is cheap, and modules are normally tiny.
Yes, all users will have shell access. Hence I had envisaged providing a few
modules only in the system default location (@INC), preferably all managed via
RPM; and if users require extra libs, then can download and install them via
"perl Makefile.pl PREFIX=$HOME" (or whatever the magic phrase is). They would
then have to add their own "use lib" (or set PERL5LIB etc).
Hence, users have the power to use whatever the modules they want, and they
also have the responsibility for making it work.
As I said a few years ago upgrading /usr/bin/perl itself would have been a
total pain too, but I don't anticipate having to upgrade perl much now.
PGP key: http://rudolf.org.uk/pgpkey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://mail.pm.org/pipermail/miltonkeynes-pm/attachments/20060122/cfbd4271/attachment.bin
More information about the MiltonKeynes-pm