Date: Fri, 29 May 1998 20:30:45 -0400 (EDT)
Message-Id: <199805300030.UAA27813@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: nate AT cartsys DOT com
CC: djgpp-workers AT delorie DOT com
In-reply-to: <19980529235344.AAF16281@ppp116.cartsys.com> (message from Nate
	Eldredge on Fri, 29 May 1998 16:54:05 -0700)
Subject: Re: Links to links
Precedence: bulk


> 1. Make the stub exec `loadname', instead of loading directly from it. I

Too complex.  The stub's symlink facilities are very crude; they were
designed to handle the simple cases like fgrep/grep.  If you want real
symbolic links, install Linux.

> 2. Make `symlink' fail if it tries to create a link to a link. How that

Can't.  The target file might not yet exist, or might change in the
future.  We have to rely on it dealing with the runtime conditions.

> 3. Change the message to something less confusing to a newbie, and have the

No.  The virus threat is *real* and warning them about it is very
important.

> 4. Document it. There may be problems; perhaps some Unix makefiles expect

Yes.  Perhaps the symlink program could print a *warning* if it can't
prove the target is a COFF program, but I think that's the best we can
do.