This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: RFC: setup package in Base
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: "cygwin-apps at cygwin dot com" <cygwin-apps at cygwin dot com>
- Date: Fri, 6 Jul 2018 14:51:51 +0100
- Subject: Re: RFC: setup package in Base
- References: <83590d14-5d6d-7536-5e79-3a03e5d3dc02@cygwin.com> <a04ffa5a-a563-f20a-b663-275fc71f9a33@cornell.edu> <5fff11ac-586d-f27e-f0f2-99aafe30f206@dronecode.org.uk> <d8d715f6-73b3-3ab6-5803-d7cdbd815198@cornell.edu>
On 05/07/2018 19:34, Ken Brown wrote:
The instruction that setup currently emits telling you to update setup
won't make a lot of sense if setup is then going to update itself
I'm attaching a patch to setup that adds a new option,
--no-version-warning, to suppress that warning. (The patch also
slightly rewords the warning.) Two further patches, to setup.cygport
and cygsetup.in, make the setup shortcuts and the cygsetup script use
that option.
Thanks for the patch.
The version is checked (again), at ini.cc:404
I've never understood why we have this twice.
(I think the idea might be that first we are checking the setup version
as a proxy for the setup.ini format version, to warn if there might be
problems parsing it. The second time we are checking the setup version
to see if an upgrade of setup is possible)
Surely the advice should be to update the 'setup' package, rather than
to use it?