On Monday, Nov 18, 2002, at 12:22 US/Pacific, Martin Redington wrote: [..]
I might not hate the stock perl enough to blow it away, but having it obscured by the PATH variable is exactly what I want.[..]
Of course, there is an issue with the instinctive #!/usr/bin/perl, with this approache, and I've been bitten by that once or twice.
p0: oh we do so agree, on both
a) that 'build and install our own' and do not always want to blow the others away
{ I have the Sun version of their perl built stuff as is where they installed it,
I just do not look for it, or really care - but I do include the places
where they add to the @INC - so that I can use their OS specific tricks.
this I fixed by rebuilding my version of perl...
note:
vladimir: 518:] head `which kstat`
#!/usr/perl5/bin/perl
#
# Copyright (c) 1999, 2001 by Sun Microsystems, Inc.
# All rights reserved.
#
#ident "@(#)kstat.pl 1.3 01/11/09 SMI"
require 5.6.1;
use strict;
use warnings;
vladimir: 519:]
They at least did their installation out of the way and call out
for themselves what they expect... a strategy some may want to adopt,
avoid, improve upon.... }
b) as well as the usual number of times that things were 'feature rich'...
{ nothing against "Old Guys" - but some folks 'do not get perl' - and
so after myFascistHouseMate bollocked the process of how to build
and install it, I got tagged with 'defining the process' - in a way
that makes it easy for him to 'just rebuild as needed' - but it's on
my head to do the CPAN builds and installs... Some folks all believe
in the CPAN.pm - and I'll back that for anyone who does not want to
become a perlMonk - and just wants it to work.... But I will argue
that if you want to grow your perl skills -
download the tarball from the CPAN/source-forge/<place>/<otherPlace>
build it
rip it apart
understand those comment bars where it says
# wish we had ....
avoid all of those in your new cooler module, application, .....
}
p1: I'll confess that I have not had the time to play with fink, that I
would prefer - but I so understand the underlying 'name space management problem'
coming as one who has to deal with developing across the vagaries of *nix.
Nothing like a 'unix standard'....
8-)
p2: The challenge of course is where John A. will feel at home...
ciao
drieux
---
