X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=XI3/aLHVgkXFGMm/
	iAT/YJWkT598RwNxhB9/zOOcgeVdv5JJqyIlim0I3HNCRBt8G2QEaXpyWgIiM82a
	9jEYXzAU8iHyiuuf+p9S4jjL5oDpBnPknwfgAFm3DDFsUC+RDtv7EhqELhfdyd7r
	LzwSoTF/4gPR4Hzf8mSnJEb+Bzo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=3TLBkyfx0ApTf1JyGVjwku
	l+83I=; b=sndlJl30oWwvyIYEaBCn2ZKr/6ZeHavUj36S1820h91aNKZQ5PBxgD
	ESjEZRPTEBtRJ9PNZBJMd7IGGa6Hw5gdsz0pwkw0kvJB13GXIytk90U+reBqY0Ua
	PeH0VEvJQ4S1LGJRwxVJePont9bMNmT39/XGetGLEe/WqGwXWGx7E=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Hx-languages-length:1235, H*Ad:D*nl, Hx-spam-relays-external:ESMTPA, documents
X-HELO:	out4-smtp.messagingengine.com
X-ME-Sender:	<xms:AMEBWtrEQcgtPjDDNj8DXx56M6PZa1B9RTdEGSOv12IcrkxBmc0qoA>
Subject:	Re: setup.ini has multiple "prev" entries ... Why?
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<20e5f0520f9831ecd59e509dc7f7d852 AT xs4all DOT nl> <fa73b1f580569c798dbe8c3867b6a01d AT xs4all DOT nl> <d62f76d8-5f85-5de6-caf2-7f4b933f861c AT dronecode DOT org DOT uk> <87tvy7e15r DOT fsf AT Rainer DOT invalid> <7b7758f7e2017b5c236b96adb4a1efb4 AT smtp-cloud9 DOT xs4all DOT net>
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Cc:	Houder <houder AT xs4all DOT nl>
Message-ID:	<37b4645e-630c-d2eb-3229-4dfb275dda12@dronecode.org.uk>
Date:	Tue, 7 Nov 2017 14:19:42 +0000
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version:	1.0
In-Reply-To:	<7b7758f7e2017b5c236b96adb4a1efb4@smtp-cloud9.xs4all.net>

On 07/11/2017 10:25, Houder wrote:
> On Mon, 06 Nov 2017 19:02:08, Achim Gratz wrote:
>> Jon Turney writes:
>>> Since [1], there's no way to install a prev version using setup,
>>> without explicitly selecting which version you want, so the ordering
>>> of those [prev] versions in setup.ini is relatively unimportant.
>>
>> For setup that is true, but linear parsers that can only keep one
>> version for each section would benefit if the last [prev] section was
>> the one that immediately precedes [curr].  So it would be helpful if you
>> could ensure it's done that way and state it in the documentation.
> 
> Agreed! A linear parser of setup.ini would _definitely_ benefit if
> 
>   - the "current" section,
>   - the most recent [prev] section, and
>   - the most recent [test] section
> 
> would have a "fixed" position relative to the package section. I concur.

I'd much rather put things in version order, but it seems that is 
impossible.

I've added a sentence to the description of setup.ini which documents 
the position of preferred [test] and [prev] sections.

Note that it is 'previous' in the sense of 'version comes before the 
current version', not 'previously was current'.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -