public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request for feature: more flexible setup routine
Date: Sun, 25 Jul 2010 20:12:00 -0000	[thread overview]
Message-ID: <AANLkTik0XnKsCvq_moPP60Dm95qvnDcm8346+01EaHyt@mail.gmail.com> (raw)
In-Reply-To: <20100725025446.GA17000@ednor.casa.cgf.cx>

On 25 July 2010 03:54, Christopher Faylor wrote:
> On Sat, Jul 24, 2010 at 07:10:08PM -0500, Marshall Abrams wrote:
>>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.
>
> *Although* you should be able to set everything to "keep" and just
> update the one package that you want

... by simply clicking on the Keep button near the top of the package
selection screen.

This makes me wonder whether Keep shouldn't be the default, on the
principle that programs shouldn't do anything unless the user asks for
it.

Also, if you're trying to stick with a proven install, forgetting to
click Keep is much worse then if you're trying to stay up-to-date yet
you forget to change from Keep to Curr. In the first case, you need to
restore a backup assuming you have one, whereas in the second you just
need to run setup again.

Yet of course the argument for having Curr as the default is that we
want to encourage users to update to the latest versions as we can't
support a myriad of different combinations of old package versions.

Hmm. How about leaving the default as is but remembering the state of
Keep/Curr/Prev/Exp across setup.exe invocations? Would a patch for
that be welcome?

Andy

--
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

  reply	other threads:[~2010-07-25 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25  2:54 Marshall Abrams
2010-07-25  3:00 ` Christopher Faylor
2010-07-25 20:12   ` Andy Koppe [this message]
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=AANLkTik0XnKsCvq_moPP60Dm95qvnDcm8346+01EaHyt@mail.gmail.com \
    --to=andy.koppe@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).