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: Mon, 06 Nov 2017 14:20:00 -0000 [thread overview]
Message-ID: <d62f76d8-5f85-5de6-caf2-7f4b933f861c@dronecode.org.uk> (raw)
In-Reply-To: <fa73b1f580569c798dbe8c3867b6a01d@xs4all.nl>
On 05/11/2017 17:32, Houder wrote:
> On 2017-11-05 13:48, Houder wrote:
>> After I had downloaded and exercised setup version 2.882, I noticed
>> that setup.ini has multiple (2?) "prev" entries per package ...
>>
>> Why? Did I miss one of your announcements mentioning this change?
>
> Â Â Â https://cygwin.com/ml/cygwin-apps/2017-10/msg00047.html
>
>> Because of the way setup works, the last [test] section is the version
>> which
>> is selected when 'test' is selected, so a specific ordering of the
>> sections
>> Â would be required. ...
>>
[...]
> So ... if I read the above correctly, the "prev" entries can be ordered
> arbitrarily with respect to each other (within a package section) ?????
> (and basically, the same question with respect to the "test" entries)
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.
[1] https://cygwin.com/ml/cygwin-apps/2011-07/msg00064.html
However, you can tell setup to install "the test version", so we ensure
that the highest version [test] section is last, to ensure it's the one
that setup installs.
> Meaning, one has to "interpret" the version id of each "prev" entry,
> in order to be able to establish the _latest_ "prev" entry (i.e. the
> version of the package before the current one) ?
Yes.
(Although due to historical mistakes with version numbers, that ordering
might be wrong)
--
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
next prev parent reply other threads:[~2017-11-06 14:20 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 [this message]
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
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=d62f76d8-5f85-5de6-caf2-7f4b933f861c@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).