Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Tue, 23 May 2000 15:41:42 -0400
To: cygwin AT sourceware DOT cygnus DOT com
Cc: Jason DOT Tishler AT dothill DOT com
Subject: Re: CygUtils Version of zip (and Symlinks)
Message-ID: <20000523154142.A24445@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com, Jason DOT Tishler AT dothill DOT com
References: <392ACD0A DOT D946A741 AT dothill DOT com> <20000523143422 DOT A22579 AT cygnus DOT com> <392AD8CC DOT 63B2436E AT dothill DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <392AD8CC.63B2436E@dothill.com>; from Jason.Tishler@dothill.com on Tue, May 23, 2000 at 03:15:24PM -0400

On Tue, May 23, 2000 at 03:15:24PM -0400, Jason Tishler wrote:
>Chris,
>
>Chris Faylor wrote:
>> If I am understanding what you're saying correctly, you are essentially
>> trying to break cygwin's encapsulation of symlinks.  There is no
>> guarantee that a symlink will always begin with "!<symlink>" or
>> even that the contents will contain any kind of magic denoting a symlink.
>
>That is why I called it a "very nasty hack."  I'm try to elicit the
>proper way to read the (raw) contents of a Cygwin symlink file -- if
>one exists.  Sounds like one doesn't.

Actually, my version of zip for cygwin has a '-y' option that stores symlinks
and unzip seems to restore them correctly.

So, this is at least possible already.

cgf

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