Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <392AE763.C5F14D7C@ece.gatech.edu>
Date: Tue, 23 May 2000 16:17:39 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: Jason Tishler <Jason.Tishler@dothill.com>
CC: cygwin@sourceware.cygnus.com
Subject: Re: CygUtils Version of zip (and Symlinks)
References: <392ACD0A.D946A741@dothill.com> <200005231838.OAA23850@envy.delorie.com> <392ADC53.8CC580B6@dothill.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

About CygUtils' zip/unzip distribution:

The zip/unzip distro at CygUtils in the V1.1 tree was recently updated
(Apr 21, 2000). Before, I had zip-2.2 and unzip-5.32, built as unix
apps, but with locally maintained, cygwin specific patches. Cosmin Truta
told me that recent versions of those packages included cygwin support,
but that Cygwin was regarded as a Windows platform:

[Cosmin Truta wrote:]
> > Therefore, the compilation is
> > 
> > make -f win32/makefile.gcc
> > 
> > for both Cygwin and Mingw32.
> > The files produced have the HostOS value equal to 11 (WinNT filesystem),
> > not 3 (Unix), and the NTSD descriptors are also stored in the zip archive,
> > along with the universal time (as in the Unix versions).

This sounded like a good thing (especially with the ntsec stuff which
uses NTSD descriptors) so the current versions (zip-2.3, unzip-5.41) on
CygUtils are built using win32/makefile.gcc.

I did not look too closely at the code; perhaps the symlink handling
stuff that is there for Unix platforms, gets #ifdef'd out in this
configuration? If so, it shouldn't be too hard to locate that section
and #ifdef it back in for __CYGWIN__. 

I've been waiting for *my* chance to say this:

Patches gratefully accepted. :-)

--Chuck


Jason Tishler wrote:
> 
> DJ,
> 
> DJ Delorie wrote:
> > > 1. What is the best way to read the contents of a symlink file?  Can I
> > > use open or do I have to resort to CreateFile?
> >
> > Use readlink() and symlink() to read and create symbolic links.  These
> > also work under unix.
> 
> I had already considered the above but if I build zip/unzip as
> recommended then there is nothing in the archive to indicate that a
> file is a symlink except for the system attribute which is ambiguous.
> Hence, unzip will not be able to determine when to call symlink.
> 
> I will looking into building zip/unzip as a UNIX version and then
> see what else breaks...
> 
> Jason
>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com