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
Subject: Re: /setup.html please read - feedback desired
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: cygwin-apps AT cygwin DOT com
In-Reply-To: <20011102134846.H26975@redhat.com>
References: <1004700277 DOT 7488 DOT 2 DOT camel AT lifelesswks>
	<3BE2E3D3 DOT 1050201 AT ece DOT gatech DOT edu>  <20011102134846 DOT H26975 AT redhat DOT com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1004745374.9086.77.camel@lifelesswks>
Mime-Version: 1.0
X-Mailer: Evolution/0.15 (Preview Release)
Date: 03 Nov 2001 10:58:58 +1100
X-OriginalArrivalTime: 03 Nov 2001 00:03:14.0245 (UTC) FILETIME=[EECCAF50:01C163FA]

On Sat, 2001-11-03 at 05:48, Christopher Faylor wrote:
> On Fri, Nov 02, 2001 at 01:20:03PM -0500, Charles Wilson wrote:
> >Robert Collins wrote:
> >
> >
> >In the "Package file naming" section:
> >"In the event that a package doesn't sort correctly (for example, from 
> >...-9-... to ...-10-..., use the setup.hint current, prev and exp labels to 
> >override the inbuilt sort during the transition period."
> >
> >I think setup.hint's are more-or-less required, now.  Otherwise, there's no 
> >way to set the sdesc, ldesc, dependencies, etc.  So, the "auto-sort" is a 
> >soon-to-be-vestigial feature; emphasis should be on setup.hint.
> 
> I don't think there is any reason to force the versioning in setup.hint.
> That's sort of error-prone, actually.  Experience has shown that.

OTOH it's the only way we can have
"really stable"
"should be stable" and
"use at own risk"

all available via setup.exe and clearly identified. Without setup.hint,
a single file is *assumed* to be current. IMO, that's dangerous as we
get more packages.

Rob