Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3E5F9E9C.6A00AA6E@ieee.org> Date: Fri, 28 Feb 2003 12:38:36 -0500 From: "Pierre A. Humblet" X-Accept-Language: en,pdf MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: Releasing new sh-utils now with access() change? References: <20030228170058 DOT GA9681 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > Pierre, > There is no reason for me to hold off on releasing a new sh-utils, with > the eaccess -> access change now, right? /bin/test won't work any worse > than it does already with this change, right? > > cgf Chris, I would not release a new /bin/test until 1.3.21 is out. With 1.3.20 the behavior will be different, sometimes better, sometimes worse. In particular the current /bin/test always produces correct results on files created by Cygwin, while sh (and the new /bin/test ) currently don't. /> ls -l test3 ---x-wxrwx 1 PHumblet Users 0 Feb 18 16:20 test3* /> if /bin/test -r test3 ; then echo yes; else echo no; fi no /> sh -c 'if [ -r test3 ] ; then echo yes; else echo no; fi' yes <== WRONG /> bash -c 'if [ -r test3 ] ; then echo yes; else echo no; fi' no Pierre