Message-Id: <199901082127.VAA20686@out4.ibm.net>
From: "Mark E." <snowball3 AT usa DOT net>
To: djgpp-workers AT delorie DOT com
Date: Fri, 8 Jan 1999 16:28:13 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: shell utils 1.16 question
In-reply-to: <199901081859.NAA02941@envy.delorie.com>
References: <Pine DOT LNX DOT 3 DOT 93 DOT 990108195028 DOT 5351C-100000 AT acp3bf> (message from	Hans-Bernhard Broeker on Fri, 8 Jan 1999 19:54:42 +0100 (MET))
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com

> I think a suitable compromise would be to allow -f to detect foo.exe,
> but when it does, print a warning: "Warning: test -f foo assumed you
> wanted foo.exe".
> 

I can live with this and the other change I suggested. But after thinking 
about it, I've concluded the best way to handle the test -f vs. autoconf is 
to submit a patch to change "test -f" to "test -x" at certain places in 
AC_CHECK_PROG and AC_PATH_PROG in autoconf. That way 
everyone is happy and then it will solve the need to regenerate 
configure scripts once the changes start being used being the gnu 
package maintainers.

Mark

--- 
Mark Elbrecht snowball3 AT usa DOT net
http://members.xoom.com/snowball3/