[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with egrep and fgrep
From: |
Bob Proulx |
Subject: |
Re: problem with egrep and fgrep |
Date: |
Fri, 3 Sep 2004 01:31:11 -0600 |
User-agent: |
Mutt/1.3.28i |
Ralph Corderoy wrote:
> > Because hardwired paths just as easy to break, both on purpose and
> > accidentally, as the PATH search method which you stumbled over.
>
> That doesn't ring true. Certainly, after `make install', it isn't
> expected that a package will work other than where it has been
> installed, unless something like GNU Stow is used to patch things up, so
> there seems little reason why the egrep script can't hardcode grep's
> location.
I often use tools installed on an NFS server on an NFS client. Others
use tools on AFS clients where the install path is not the same as the
usage path.
Bob
Message not available
- Message not available
- Re: problem with egrep and fgrep, Ralph Corderoy, 2004/09/02
- Re: problem with egrep and fgrep,
Bob Proulx <=
- Message not available
- Re: problem with egrep and fgrep, Ralph Corderoy, 2004/09/07
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/12
- Re: problem with egrep and fgrep, Paul Jarc, 2004/09/13
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/13
- Re: problem with egrep and fgrep, Paul Jarc, 2004/09/13
- Re: problem with egrep and fgrep, Eli Zaretskii, 2004/09/13
- Message not available
- Re: problem with egrep and fgrep, Eric Backus, 2004/09/13
- Re: problem with egrep and fgrep, Bob Proulx, 2004/09/15
- Message not available
- Re: problem with egrep and fgrep, Eric Backus, 2004/09/15
Re: problem with egrep and fgrep, Bob Proulx, 2004/09/12