Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Date:	Fri, 16 Nov 2001 18:36:58 EST
To:	cygwin-apps AT cygwin DOT com
Cc:	Corinna Vinschen <vinschen AT redhat DOT com>
Subject:	Re: clickable categories
X-Mailer:	Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va
Message-Id:	<VA.000009b5.01d1e604@thesoftwaresource.com>
From:	Brian Keener <bkeener AT thesoftwaresource DOT com>
Reply-To:	bkeener AT thesoftwaresource DOT com
In-Reply-To:	<20011116194319.GO17035@redhat.com>
References:	<007a01c16e5f$0ddc1480$0200a8c0 AT lifelesswks> <20011116112720 DOT F14456 AT cygbert DOT vinschen DOT de> <20011116194319 DOT GO17035 AT redhat DOT com>

Christopher Faylor wrote:
> >> *  the category has a spin control, and on clicking this, sets all
> >> packages to the closest match possible for the spin control. I.e. if the
> >> category is set to prev, an a package has no prev, the package goes to
> >> "installed version" or "curr".
> >
> >This one, IMO.
>
I like the closest match option - I think at one time on the old setup we had 
it so on each package if it was not installed or an older version that what was 
in setup.ini was installed then if you clicked curr - setup would try to 
install the current but if you did not have the curr version but you did have 
the prev version - then setup would try to install the prev version. And if you 
selected test - it would go from test to curr to prev and if none of those were 
available then setup would keep the installed version.  I think this logic 
should be used in category selection and individual package selection.  

I was working on this on the pre-category branch (the one right after some of 
the major rewrites when setup.ini had started to change) when I realized how 
little I now knew about setup.  Never got it working completely.  One other 
thing I noticed when doing this though - when the package version being 
installed is displayed it helped if I appended a "(curr)" or "(prev)" or a 
"(test)" on the display to show the user which version from setup had been 
selected.

My $.02.

bk

- Raw text -