From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: AW: documentation archive
Date: Wed, 20 Dec 2000 11:37:00 -0000 [thread overview]
Message-ID: <00122020370103.08590@cygbert> (raw)
In-Reply-To: <200012201918.LAA29435@prosper.leonora.org>
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.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2000-12-20 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 6:21 Earnie Boyd
2000-12-20 11:18 ` Vladimir G Ivanovic
2000-12-20 11:33 ` Larry Hall (RFK Partners, Inc)
2000-12-20 11:37 ` Corinna Vinschen [this message]
2000-12-20 11:40 ` Christopher Faylor
2000-12-20 13:43 ` Corinna Vinschen
2000-12-20 17:19 ` Robert Collins
2000-12-20 17:29 ` Christopher Faylor
2000-12-20 17:37 ` Robert Collins
2000-12-20 20:01 ` Charles Wilson
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 14:39 Andreas Eibach
2000-12-20 11:39 Earnie Boyd
2000-12-19 6:15 klaus.berndl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00122020370103.08590@cygbert \
--to=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).