Re: command not found on remote server

[Ken Irving]

On Thu, Dec 11, 2008 at 03:35:33PM -0700, Bob Proulx wrote:
> Paul Jarc wrote:
> > Bob Proulx wrote:
> > > Also, using full paths is frowned upon.
> > 
> > You mean invoking /directory/some-command directly instead of
> > PATH=$PATH:/directory
> > some-command
> > ?
> ...
> ... I was actually commenting on a previous suggestion earlier in
> the thread that full paths be used.  I was compelled to object to that
> suggestion.
> 
> I have seen too many scripts that people write with full paths
> *thinking* that they are making the script stronger when in reality
> they are making it more fragile.  More fragile because they are then
> fixing the script into the rigid framework of a particular system.
> That is the case I am frowning upon.

I've often used hard-coded paths, and appreciate your argument and
reasoning.  Makes sense to me, and I'll try to change my ways.  Thanks!

Ken

-- 
Ken Irving