Web lists-archives.com

Re: setup.ini has multiple "prev" entries ... Why?




On 06/11/2017 16:34, Houder wrote:
On 2017-11-06 15:20, Jon Turney wrote:
[snip]

I try to keep [1] accurate and up-to-date, but the 'specification' is
really "what setup accepts" :(

Currently, the ordering requirements are:

1) The version to be installed when test versions are selected (the
highest test, unless one is explicitly specified in override.hint) is
the last [test] section

2) [curr] is first

But since both these things are to work around historical setup
limitations, I don't think they merit mention in [1], and might not be
the case in a future when we no longer care about setup versions old
enough to need them.

[1] https://sourceware.org/cygwin-apps/setup.ini.html

But if the order of the versions is to be based _solely_ on "version",
which until now was merely an identifier (like "aap", "noot", "mies"),

In fact, setup makes some decisions based on label, and some based on version ordering, which part of the current mess...

that is without any order, then both semantics and syntax of "version"
must be rigidly defined in [1] ...

... if you want it to be a specification for setup.ini.

I'm not sure it belongs there, but the ordering is defined (see [2])

[2] https://cygwin.com/packaging-package-files.html#naming

--
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