Re: [PATCH setup] Add setup-minimum-version: to setup.ini

[Jon Turney <jon.turney@dronecode.org.uk>]

On 26/02/2018 17:10, cyg Simple wrote:
> On 2/26/2018 9:02 AM, Jon Turney wrote:
>> This allows setup.ini to require a certain setup version, rather than advise
>> a newer version when one is available.
>>
>> Unfortunately, versions of setup prior to this one don't implement this, but
>> at least we have this going forward.
>>
>> When we want to start using this, we can break backwards compatibility with
>> even older setup in a less clean way, simply by using setup.ini grammar that
>> they can't parse.
> While you're breaking backward compatibility may I be so bold as to

Um, what?  This doesn't do anything of the sort.

> suggest a change in the name of setup EXE to include the version of
> setup?  And then with that change a query to the user to download and
> use the newest version of setup?

This will break more than backwards compatibility with old versions of 
setup, but also any scripts that do 'wget -N 
https://cygwin.com/setup-x86_64.exe', or equivalent.

It also invalidates a lot of written references to this executable, so 
we should probably only make this change with good reason.

> The change stems from a long standing desire to do just what I've
> described.  Since setup knows that it is out of date why force the user
> to exit it, go to cygwin.com to download the current version and then
> restart that version of setup?  The name change would allow for an easy
> method to apply a change to do the download of the newer version from
> the older version as it removes the name conflict.

You might find the code in [1] a good starting point for an alternate 
implementation, which doesn't require renaming the executable.

[1] https://cygwin.com/ml/cygwin-apps/2011-04/msg00054.html