From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Houder <houder@xs4all.nl>
Subject: Re: setup.ini has multiple "prev" entries ... Why?
Date: Tue, 07 Nov 2017 14:19:00 -0000 [thread overview]
Message-ID: <37b4645e-630c-d2eb-3229-4dfb275dda12@dronecode.org.uk> (raw)
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
prev parent reply other threads:[~2017-11-07 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 12:48 Houder
2017-11-05 14:03 ` Vince Rice
2017-11-05 14:20 ` Houder
2017-11-05 14:37 ` Houder
2017-11-05 17:32 ` Houder
2017-11-05 18:04 ` Houder
2017-11-06 14:21 ` Jon Turney
2017-11-06 15:35 ` Houder
2017-11-06 17:37 ` Jon Turney
2017-11-06 16:34 ` Houder
2017-11-06 17:37 ` Jon Turney
2017-11-06 14:20 ` Jon Turney
2017-11-06 16:15 ` Houder
2017-11-06 18:02 ` Achim Gratz
2017-11-07 10:25 ` Houder
2017-11-07 14:19 ` Jon Turney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37b4645e-630c-d2eb-3229-4dfb275dda12@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=houder@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).