Re: setup.ini has multiple "prev" entries ... Why?
- Date: Tue, 7 Nov 2017 14:19:42 +0000
- From: Jon Turney <jon.turney@xxxxxxxxxxxxxxxx>
- Subject: Re: setup.ini has multiple "prev" entries ... Why?
On 07/11/2017 10:25, Houder wrote:
On Mon, 06 Nov 2017 19:02:08, Achim Gratz wrote:
Jon Turney writes:
Since , 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
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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple