Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
X-Authentication-Warning:	modi.xraylith.wisc.edu: khan owned process doing -bs
Date:	Wed, 12 May 1999 13:41:50 -0500 (CDT)
From:	Mumit Khan <khan AT xraylith DOT wisc DOT edu>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Why you shouldn't use WinZIP on tar files [Re: texinfo install]
In-Reply-To:	<007201be9c9e$5bfe9790$47191ecc@amazon.lbin.com>
Message-ID:	<Pine.SUN.3.93.990512133537.14298B-100000@modi.xraylith.wisc.edu>
MIME-Version:	1.0

On Wed, 12 May 1999, Ian Zimmerman wrote:

> But WHY?  Sorry, I understand that I'm taking your time to ask a
> low-priority problem, but I can never be satisfied with answers of the type
> "just do this, it works".  What is it that WinZip screws up?  Is it the
> CR/LF conversion?  I turned that off.
> --

If you know what you're doing, it works just fine. The trouble is that
most users of WinZIP don't notice these hidden conversions, and a few
other things, and it takes time away from "real work" to answer these
questions or track these non-bugs. 

WinZip doesn't understand a few things that may be in the tar file:

  - hard links
  - symbolic links

and there's the damned auto-conversion.

As far as I'm concerned, you can type in the bytes using a hex editor; I 
just don't want bug reports if you miss a byte here and there.

I'm taking bets on when this issue will rear its ugly head again ;-)

Regards,
Mumit



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

- Raw text -