From: Charles Wilson <cwilson@ece.gatech.edu>
To: jmerz42@earthlink.net
Cc: cygwin@cygwin.com
Subject: Re: Press for Cygwin
Date: Thu, 30 Aug 2001 14:04:00 -0000 [thread overview]
Message-ID: <3B8EAA43.7090301@ece.gatech.edu> (raw)
In-Reply-To: <3B8EA37E.8000004@earthlink.net>
Jonathon Merz wrote:
>>
>>
>>> Does anyone know how we can adapt the archives so that they are not
>>> WinZip
>>> readable? Would just converting everything to .bz2 do that?
>>>
>>
>>
>>
>> Seems like it. WinZip 8.0 won't read a cron-3.0.1-4.tar.bz2 file I have.
>>
> <soapbox>
</me chops your soapbox up for firewood>
> Just some comments: I do fully support the use of bzip2 over gzip
> because it compresses better, but I think using it purely to thwart
> WinZip users would be a bad reason to do so.
Really? when (a) using WinZip results in a BROKEN installation, (b)
users who say "I installed cygwin using WinZip" on this mailing list are
immediately told -- "reinstall using setup.exe" (because winzip-created
cygwin "installations" are irretrievably BROKEN), and (c) because it's
technically POSSIBLE right now to "install" cygwin using WinZip, we get
newbies who ignore the HUGE @#$(& link on the cygwin webpage for the
setup program and use WinZip to "install" at least once a week --
You think we're out of line for trying to make it hard for *new users*
to shoot themselves in the foot?
> Deliberate limitations
> compatibility for the sake of limiting compatibility is something that
> many people dislike about Microsoft, and I don't see that it improves
> anything, ever.
But WinZip is ALREADY "incompatible" -- while you can "unzip" the
.tar.gz files and get something that LOOKS like a cygwin installation --
it isn't. Isn't an obvious, upfront refusal to allow this better than
enabling users to "install" a broken system by using the WRONG tool?
> On the other hand, if there is a legitimate reason to
> do something, and limiting compatibility is a side effect, then so be
> it.
DING DING DING! We have a winner!
> Likewise, while we all appreciate the efficiency of command-line
> tools, trying to thwart users of WinZip is kind of elitist, and for
> those who have gotten to be called "System Administrators" without
> learning much in the way of command line tools, our efforts would be
> better spent teaching them to patch their IIS servers before we try to
> teach them to use the command line :)
Irrelevant. Setup.exe is already a GUI tool -- despite continual
requests by "elitists" to add commandline/batch capability. These
"elitists" are not 31337 enough to do add/contribute the necessary
capabilities themselves, so it hasn't been done. So much for "elitism".
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-08-30 14:04 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 12:57 Larry Hall (RFK Partners, Inc)
2001-08-30 13:07 ` Christopher Faylor
2001-08-30 13:12 ` Larry Hall (RFK Partners, Inc)
2001-08-30 13:25 ` Christopher Faylor
2001-08-30 13:37 ` Jonathon Merz
2001-08-30 14:04 ` Charles Wilson [this message]
2001-08-30 13:29 ` Rick Rankin
2001-08-30 13:33 ` Gerrit P. Haase
2001-08-30 13:42 ` Michael Schaap
2001-08-30 13:50 ` Christopher Faylor
2001-08-30 14:01 ` Michael Schaap
2001-08-30 14:06 ` Christopher Faylor
2001-09-02 20:24 ` John Marshall
2001-08-30 13:56 ` Gerrit P. Haase
2001-08-30 14:03 ` Michael F. March
2001-08-30 14:12 ` Michael Schaap
2001-08-30 14:06 ` Charles Wilson
2001-08-31 19:52 ` Mobile install Alex Malinovich
2001-09-01 2:31 ` Dario Alcocer
2001-09-01 14:19 ` Alex Malinovich
2001-09-02 8:27 ` Dario Alcocer
2001-09-02 9:41 ` Alex Malinovich
2001-09-02 12:00 ` Dario Alcocer
2001-08-30 13:47 Press for Cygwin Robinow, David
2001-08-30 14:10 Robinow, David
2001-08-30 14:24 ` Charles Wilson
2001-08-30 14:31 yap_noel
2001-08-30 15:38 ` Eric M. Monsler
2001-08-30 14:34 press for cygwin Peter Buckley
2001-08-30 14:57 ` Christopher Faylor
2001-08-31 0:34 Press for Cygwin Peter Ring
2001-08-31 7:36 press for cygwin Mark Bradshaw
2001-08-31 8:07 ` Charles Wilson
2001-08-31 10:29 ` Larry Hall (RFK Partners, Inc)
2001-08-31 17:09 ` Robert Collins
2001-09-03 6:52 Bernard Dautrevaux
2001-09-03 7:56 ` Charles Wilson
2001-09-03 8:14 ` Christopher Faylor
2001-09-03 8:45 ` Michael Schaap
2001-09-03 9:03 ` Christopher Faylor
2001-09-03 9:30 ` Andrew Markebo
2001-09-03 9:36 ` Christopher Faylor
2001-09-03 15:23 ` Robert Collins
2001-09-03 18:23 ` Christopher Faylor
2001-09-03 19:17 ` Charles Wilson
2001-09-03 19:35 ` Robert Collins
2001-09-04 9:52 ` Warren Young
2001-09-04 12:52 ` Christopher Faylor
2001-09-05 18:04 ` Warren Young
2001-09-07 12:27 ` Warren Young
2001-09-07 12:35 ` Christopher Faylor
2001-09-07 14:22 ` Warren Young
2001-09-07 14:43 ` Christopher Faylor
2001-09-03 8:56 Bernard Dautrevaux
2001-09-05 5:04 jmarshall
2001-09-05 8:52 ` Christopher Faylor
2001-09-06 1:55 jmarshall
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=3B8EAA43.7090301@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=jmerz42@earthlink.net \
/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).