Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
Subject: RE: prev/curr/test
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Tue, 26 Mar 2002 19:27:57 +1100
Message-ID: <FC169E059D1A0442A04C40F86D9BA76008ABA7@itdomain003.itdomain.net.au>
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2Q8TmZ06385



> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Tuesday, March 26, 2002 1:09 PM

> >But a big deal at one point in time was the ability to get to 
> >packages/versions that were in the local directory and 
> install those - 
> >how else can you do this if you limit your self to prev, curr, and 
> >test.
> 
> I don't know who this was a big deal for.  It isn't for me; 
> especially if we would be confusing the people who want to 
> use setup.exe for its normal use at the expense of people who 
> have additional requirements.

Someone somewhere got bitten by an upgrade IIRC. Certainly it's not the
key focus of setup. And once setup is command line driven, this should
be less of an issue: if you know that you want version foo, just ask for
it.
 
> I think the whole cycling through versions thing was a big 
> mistake. I don't know of any other setup utility that allows 
> this kind of thing. Heck, I believe that you actually need to 
> specify a different repository entirely if you want to 
> install non-current packages in debian.
> 
> Is this correct, Robert?

Yes. Well kinda. Debian's automatic system - apt and dselect - only
allow grabbing the most recent version, or staying on your current
version. They then have three parallel distributions, one Stable, one
Testing, and one Unstable. Stable -never- breaks, Testing make break,
and Unstable... well it's your risk. For a given machine, you typically
only ever point apt at one distribution.
 
> You don't.  You find some other method for reverting to 
> software that is <1 revision old.  This is not a hardship.  
> AFAIK, setup has never allowed you to do more than prev/curr/test.

Not from the net. It does locally though FWIW.
 

> And how do you know when you've hit the current version?  You 
> see it scroll by and remember that you want "1.4.9-1 bin" and 
> then click the mouse ten more times to get back to that.  
> That's really not user friendly, IMO.

Exactly.

Rob