🚀 go-pugleaf

Tom Christiansen <tchrist@convex.COM> writes
> From the keyboard of jbotz@mtholyoke.edu (Jurgen Botz):
> :>I'm not sure, though, that I would characterize this as  
"*much*
> :>easer".  It isn't that hard to edit a file or sed a  
collection of
> :>files.
> :
> :Especially since the Camel book (the standard Perl  
reference) contains
> :a nice little Perl program to fix all the #! lines of  
scripts for your
> :system.
> 
> Imagine a /common/scripts/ directory that's mounted on a  
bunch
> of different machines of varying architectures.  You'd  
want the
> #! line to match everywhere.

Right.  But the interpreter for each architecture had  
better be in a different place or you will get an awful lot  
of 'bad magic number' errors.

I follow Dave Ross's notion.  Perl goes in /usr/local/bin  
which points to a different physical directory depending on  
architecture.  /usr/local/scripts may well be common, may  
be default on everyone's path, but again doesn't go in the  
stuff the vendor distributes.  I've had too many cases  
where the way to perform an upgrade is to reformat the hard  
disk.  No thanks.  What I install is kept on a different  
partition.  I've even started entending that notion to  
putting the volitile files in /etc on another partition,  
and replacing them with links.