Up Prev Next
From: Matthew dot Persico at Lazard dot com
Subject: Re: Sybperl2.17 Installation
Date: Sep 24 2004 1:23PM
As both a Perl programmer and the de-facto Perl environment manager here, I side
with your admin. The FIRST installation of any version of any CPAN module
should never go into the default perl tree.
We all know that Michael is an absolute computer god/genius :-), but even the
best of us make mistakes. Install it someplace else. Test it. When you are
satisfied, then ask your UNIX admin where CPAN modules are supposed to be
loaded. Chances are that the admins will update the tree, they just don't want
every Perl programmer individually willy-nilly mucking up the base tree on a box
(even a development one) that is used by more than one programmer and possbily
by the operating system itself.
Also, I tend to define installation late at the install stage:
make test install PREFIX=/mylib
That way, I don't have to re-execute (or forget to re-execute) perl Makefile.PL
every time I change the installation location.
Other random thoughts:
Only CPAN modules should end up in your Perl tree. In-house modules should be
installed someplace else and PERL5LIB should be set up in machine-level
profiles. Its a bit more bookkeeping, but it allows you to ahve different
machines for different purposes with differing modules sets and yet build one
perl distribution on a master box and copy it out to all your other boxes,
instead of rebuilding perl on each individual box. Of course, it depends on how
big your organization is.
We keep perl in /opt/perl, not /usr/local/. Why?
1) Generic catch-basins are sloppy. You never know what's in there
version-wise. You never know if you can safely replace it. They are the result
of Bad Laziness (as opposed to Good Laziness, as defined by Larry Wall) by the
those who can't find it themselves to maintain a proper PATH variable in
If you build perl with prefix = /opt/perl, you end up with
By tweaking the config even more, we have
Now I can safely install all versions of perl side by side w/o interference.
2) Most *nix distributions today come with perl in /usr/bin and it is required
for proper operating system operation. In that case, I would NEVER install CPAN
modules into the default tree. Put them someplace else and modify PERL5LIB for
all non-administrative logins only. You don't know what effect an upgrade or an
addition will have on the adminsitration of your box otherwise.
3) Perl is worthy of being treated like its own product. Why mix it with the
riff-raff in the /usr/local neighborhood?
Ok, so that was more than USD 0.02.
30 Rockefeller Plaza
New York, NY 10020, USA
Phone Number: 212 632 8255
Fax Number: 212 332 5904
To: "Li, Richard"
"Michael Peppler" cc: "Sybperl-L Mailing List"
Subject: Re: Sybperl2.17 Installation
24 Sep 2004 01:35 AM
[CC'd to sybperl-l]
On Fri, 2004-09-24 at 05:32, Li, Richard wrote:
> Hi Michael,
> I just downloaded the package and try to install it on a SunOs 5.8 box
> (Sybase 12.5) and don't know how to install it into my local directory
> rather perl tree directory.
> The default perl version is 5.8.0 and I want to use the dynamic load
> feature. The "make test' is just fine but in the last step ("make install"),
> I found no where I could define the directory which I want to install in.
You can define this when you first create the Makefile:
perl Makefile.PL LIB=~/myperllib
> directorly went into
> /usr/local/lib/perl5/site_perl/5.8.0/sun4-solaris/auto/Sybase/DBlib and
> started copying across files and got permission error of course.
> It's against our Banks' policy to copy all files into the default perl
> directory (contacted our Unix adm).
Too bad. You might want to tell your adm/management that sybperl is used
in production in thousands of banks world-wide, with many of the usesrs
on this mailing list!
Michael Peppler Data Migrations, Inc.
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short
or long term contract positions - http://www.peppler.org/resume.html