From: Ilja Umov <ilja.umov@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin installer could be much more better
Date: Wed, 29 Jan 2014 04:26:00 -0000 [thread overview]
Message-ID: <CAKYyfB08yy5QPk_w2JMPE909s0AK0H-Rmx=c5G4AUYdqLdCVtQ@mail.gmail.com> (raw)
Hi,
there is a certainly a good historical reason why cygwin installer
has so many options. But now one-click installers are so common
(Google Chrome is the best example), it may look rather scary,
especially for beginners.
I did browse a bit though cygwin source code and well, I'm not so
great at C++, that I could help in any meaningful way.
Though I did make a script that downloads and extract list of cygwin
packages (Python>=3.3, because of `.xz` files):
https://github.com/iljau/cyg_fetcher/blob/master/fetch_package_list.py
Didn't quite get to installation part, yet.
Based on my cygwin usage (installing and updating it on multiple
machines) and during process of writing above script I discovered
following:
1) Usually I want to "Install from Internet"
2) Usually "C:\cygwin" is where I want to install it for "All Users".
3) "Local Package Directory" could be just environment variable
%TMP% or %TEMP%. (Still don't understand difference)
4) Usually "Direct connection" is good.
5) The most reliable mirror is (and the only one that supports https):
https://mirrors.kernel.org/sourceware/cygwin/
6) Usually I dont want to "Create Icons", especially after update.
So there are multiple possibilities to provide reasonable defaults
and spare users from confusion.
That's probably why MSYS2 is being developed:
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2
Thank you for your attention.
--
Ilja Umov
https://iljau.me
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2014-01-29 4:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 4:26 Ilja Umov [this message]
2014-01-29 4:47 ` Josh Hunsaker
2014-01-29 5:32 ` Christopher Faylor
2014-01-29 6:57 ` Steven Penny
2014-01-29 7:06 ` Steven Penny
2014-01-29 7:28 ` Marco Atzeri
2014-01-29 14:59 ` Christopher Faylor
2014-01-29 20:40 ` iljau
2014-01-29 21:22 ` Larry Hall (Cygwin)
2014-01-29 21:48 ` Steven Penny
2014-01-29 23:45 ` Larry Hall (Cygwin)
2014-01-30 1:13 ` Christopher Faylor
2014-01-29 16:35 ` Andrey Repin
2014-01-29 17:34 ` Ilja Umov
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='CAKYyfB08yy5QPk_w2JMPE909s0AK0H-Rmx=c5G4AUYdqLdCVtQ@mail.gmail.com' \
--to=ilja.umov@gmail.com \
--cc=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).