public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Brian Gallew" <geek@burri.to>
To: <robert.collins@itdomain.com.au>
Cc: <jim.george@blueyonder.co.uk>, <cygwin@cygwin.com>
Subject: RE: Setup as recommended reading
Date: Sun, 26 May 2002 11:57:00 -0000	[thread overview]
Message-ID: <3710.128.2.120.244.1022414514.squirrel@mail.burri.to> (raw)
In-Reply-To: <FC169E059D1A0442A04C40F86D9BA7600C6163@itdomain003.itdomain.net.au>

Robert Collins said:
> There is an implicit conflict there with setup, because setup
> doesn't know what was available before - it only knows version for
> what is installed. That will change in the future.

How about this:  Allow packages to be marked "never install"?  Then
setup can display all of the udpated or new packages, yet give the
user an easy way to control what (s)he has to look at?


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

  reply	other threads:[~2002-05-26 12:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-26  8:59 Robert Collins
2002-05-26 11:57 ` Brian Gallew [this message]
2002-05-26 12:13   ` René Møller Fonseca
  -- strict thread matches above, loose matches on Subject: below --
2002-05-27  2:01 Robert Collins
2002-05-26 13:47 Robert Collins
2002-05-26 18:19 ` Nicholas Wourms
2002-05-26 12:11 Robert Collins
2002-05-26  9:05 Dockeen
2002-05-26  6:30 Robert Collins
     [not found] <30C9E24891FFD411B68A009027724CB74433DD@eg-002-015.eglin.af .mil>
2002-05-22 11:55 ` Larry Hall (RFK Partners, Inc)
2002-05-22  9:31 Keen Wayne A Contr AFRL/MNGG
2002-05-26  0:55 ` Jim.George
     [not found] ` <Pine.CYG.4.44.0205251652540.1876-100000@gateway.GEORGE.CO. UK>
2002-05-26  0:58   ` Larry Hall (RFK Partners, Inc)
2002-05-26  5:20     ` Christopher Faylor
2002-05-27  6:24     ` Jim.George

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=3710.128.2.120.244.1022414514.squirrel@mail.burri.to \
    --to=geek@burri.to \
    --cc=cygwin@cygwin.com \
    --cc=jim.george@blueyonder.co.uk \
    --cc=robert.collins@itdomain.com.au \
    /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).