From: "Marshall Abrams" <mabrams001@bham.rr.com>
To: <cygwin@cygwin.com>
Subject: Request for feature: more flexible setup routine
Date: Sun, 25 Jul 2010 02:54:00 -0000 [thread overview]
Message-ID: <30EAF1C130A74F97AC4C82B42ED55DAE@hometoshiba> (raw)
I *love* Cygwin. I use it to get my work done every day. I am grateful to
everyone who has contributed to it over the years and continues to do so.
Thank you. That bears repeating: Thank you!
I have one suggestion: I wish that the setup routine was better for... users
like me who mainly want to get work done, don't care necessarily care
whether we have the latest versions of every package (honestly, most of
package changes are irrelevant to most people most of the time (OK, until
you need it...)), and more than anything else, don't want to break anything
that works.
One of the beautiful things about Cygwin's setup.exe is that when--perhaps
in the middle of trying to get something done before a deadline--I realize
that a Cygwin package I didn't think I'd need would help. If it hasn't been
*too* long since I last installed, I go and mark the package to install,
carefully make sure that I mark all other new packages as "keep", and hit
next. Great. The 1.7 upgrade has made that a pita. I am *not* going to
install 1.7. Not now. I'm in the middle of a project. I just wanted one
little tool.
What I hope will be added is some way to allow setup.exe to look farther
back in the past, or automatically ignore most package releases.
Something--something so that I can get the functionality of setup.exe for
one or two packages when I haven't updated anything for while--because it
was working fine! And I don't fix what's not broken.
(I never install everything--I'd be willing to waste the disk space, but too
often incompatibilities break things. That's also why I don't upgrade what
doesn't need upgrading. One time in five something is installed that screws
up something I had working. That's not a complaint; it's inevitable with a
complex system. I also don't regularly upgrade everything, because when I
do I sometimes have to fix something major, or just fix some packages that
has been "improved" in such a way that I can no longer work the way I want
without undoing something and recustomizing it. Again: Inevitable with a
complex system.)
Last but not least--I can't say it enough:
Thank you!
Marshall Abrams
marshall@logical.net
--
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:[~2010-07-25 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 2:54 Marshall Abrams [this message]
2010-07-25 3:00 ` Christopher Faylor
2010-07-25 20:12 ` Andy Koppe
2010-07-26 11:52 ` Andrey Repin
2010-07-26 12:12 ` Andy Koppe
2010-07-26 15:15 ` Christopher Faylor
2010-07-26 15:19 ` Andy Koppe
2010-07-26 19:25 ` Christopher Faylor
2010-07-27 17:49 ` Andy Koppe
2010-07-27 19:40 ` Christopher Faylor
2010-07-26 19:27 ` Andrey Repin
2010-07-25 4:02 ` Daniel Colascione
2010-07-25 20:08 ` Jeremy Bopp
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=30EAF1C130A74F97AC4C82B42ED55DAE@hometoshiba \
--to=mabrams001@bham.rr.com \
--cc=cygwin@cygwin.com \
--cc=marshall@logical.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).