Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <20000326230229.29455.qmail@web802.mail.yahoo.com>
Date: Sun, 26 Mar 2000 15:02:29 -0800 (PST)
From: Rick Rankin <rick_rankin AT yahoo DOT com>
Subject: Re: No such file or directory
To: Cygwin <cygwin AT sourceware DOT cygnus DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I wasn't necessarily saying that it is the "wrong" solution, just that it needs
to be considered carefully. I wasn't aware that other POSIX layers (I assume
you are referring to UWIN or similar) have sucessfully implemented a similar
feature. I haven't thought it through, but on the surface, it does seem that it
could solve many compatability issues.

If you decide to implement it, should it be selectable via, for example, a
CYGWIN environment variable setting?

Rick
--
Rick Rankin
rick_rankin AT yahoo DOT com

--- Chris Faylor <cgf AT cygnus DOT com> wrote:
> On Sat, Mar 25, 2000 at 08:13:08PM -0800, Rick Rankin wrote:
> >I don't know.  I think you'd want to consider it very carefully.  I'd
> >be pretty annoyed if I typed 'cat foo', thinking foo contained a few
> >lines of text, and cat instead opened foo.exe because I was in the
> >wrong directory or something like that.
> >
> >It seems like most of the problems you refered to are related to make
> >and/or install.  Wouldn't it be better to "fix" these programs than to
> >build something like this into the core?
> 
> The problem is already "fixed" in install but that doesn't "fix" the
> problem for packages that don't use "install".
> 
> So, the only other alternative is to modify, cp and mv.  I guess we
> could also change every open in make but I don't think that's the
> right solution.
> 
> Other POSIX-over-Windows packages seem to default to finding a ".exe".
> I don't think this would be too burdensome, myself.
> 
> cgf
> 
> >--- Chris Faylor <cgf AT cygnus DOT com> wrote:
> >> I wonder if it would really be a big deal if cygwin, by default, found a
> >> file "foo.exe" if there was no existing file "foo".
> >> 
> >> We keep running into this problem and I wonder if implementing this in
> >> cygwin would solve more problems than it causes.
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com