Date: Sun, 14 Nov 1999 16:08:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: First alpha symlink patch
In-Reply-To: <382EB0D0.1A3E63E8@softhome.net>
Message-ID: <Pine.SUN.3.91.991114160607.20280A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 14 Nov 1999, Laurynas Biveinis wrote:

> I just chose GNUish way; I like it and it wasn't very hard to
> implement. To be bulletproof, I also record the real name of
> directory - if it does not match with what DOS call returns, do 
> not return symlink.

I don't like static global variables: they are evil in recursive 
situations.

> IMHO, if DOS/Windows 
> non-DJGPP and non-CygWin applications do not see them, that's not a big 
> problem - they won't know what to do with symlinks anyway.

What I had in mind was a situation when someon zips a DJGPP directory 
tree and then moves it to another machine, or uses some recursive copy 
program to do similar things.  If that program or that archiver don't 
copy or don't put the symlink files, you will have a subtly broken 
installation in the new place.