Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <018e01c296ed$4ab4e5a0$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Kris Thielemans" <kris DOT thielemans AT csc DOT mrc DOT ac DOT uk>, <cygwin AT cygwin DOT com>,
   <cygwin-apps AT cygwin DOT com>
References: <NBBBKKHEOHOEPNCALMIGMEKFDIAA DOT kris DOT thielemans AT ic DOT ac DOT uk>
Subject: Re: setup feature request (THREAD MOVING to CYGWIN-APPS)
Date: Thu, 28 Nov 2002 14:49:02 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Setup design discussion happens on cygwin-apps AT cygwin DOT com.
This thread is moving there.

Everybody, please remove cygwin AT cygwin DOT com from your replies.

--------------------------------------------------------------------

Kris Thielemans <kris DOT thielemans AT csc DOT mrc DOT ac DOT uk> wrote:

> I'd like to have an additional radio-button in setup called 'keep'
> (that's in addition to curr, exp, prev). Why? I often do NOT want to
> update a whole bunch of stuff, but just 1 particular package. (This
> happens most often when I'm working at home via a sloooow modem, but
> in other cases as well). At the moment, this involves a painful
> process of going through the whole list, clicking multiple times such
> that 'keep' is listed, except for that one precious package...
>
> Useful? (yes)

I agree.

> Will it be implemented? (I hope so, and the implementer can get a
> really nice email from me).

I volunteer. But I suggest we remove the prev radio button - it really
doesn't make any sense to replace a load of packages with previous versions,
when one could be a few days old, but others could be a year old - it all
depends on the release schedules of the seperate packages.

Comments?

I'm not promising anything, but there's a slim chance I'll have a patch
ready in time for upcoming setup release at the weekend / early next week.

Max.


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