Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 20 Dec 2000 14:40:07 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: AW: documentation archive Message-ID: <20001220144007.F21461@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200012201918 DOT LAA29435 AT prosper DOT leonora DOT org> <00122020370103 DOT 08590 AT cygbert> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <00122020370103.08590@cygbert>; from cygwin@cygwin.com on Wed, Dec 20, 2000 at 08:37:01PM +0100 On Wed, Dec 20, 2000 at 08:37:01PM +0100, Corinna Vinschen wrote: >On Wednesday 20 December 2000 20:18, Vladimir G Ivanovic wrote: >> EB> 2) Don't use Winzip to explore a cygwin archive file. >> >> I do this as well without problems, although it's not my preferred >> way of exploring a gzipped tar gile. WinZip will ask if it should >> decompress the file to a temporary directory and open it, which it >> does admirably. Also, see below. > >This is an old discussion. WinZip has three problems which are very >annoying. > >- tar archives are extracted with CR/LF conversion by default. This > can be switched off fortunately by a config dialog. > >- It doesn't create empty directories from the archive. > >- Worst: It doesn't know of Cygwin symbolic links so they are extracted > without setting the system bit. > >That's it and these are the reasons for suggesting not to use WinZip >for unpacking. Especially newbies will not be able to figure what's >gone wrong. I wonder if we can add a bit to our version of tar to make it produce files that are unextractable using winzip. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple