From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: "Peter A. Castro" <doctor@fruitbat.org>
Subject: Re: setup release candidate - please test
Date: Mon, 08 May 2017 21:55:00 -0000 [thread overview]
Message-ID: <cf7b76a7-ba72-4cef-cb7c-bdc06fe96ac2@dronecode.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1705081110180.11764@ming.fruitbat.org>
On 08/05/2017 19:26, Peter A. Castro wrote:
> On Mon, 8 May 2017, Jon Turney wrote:
[...]
>>
>> - Add --allow-unsupported-windows option
>> Don't check the windows version.
>
> Huzzah!! Thanks for this!!
No problem.
>> The Cygwin mirror list is not read, so a URL (e.g. a Cygwin time
>> machine circa) should be given with --site or via the GUI.
>>
>> - Remove support for some long-obsolete setup.ini syntax (omitted
>> version:, omitted size and checksum, various undocumented tokens)
>
> Can you tell me what Setup will do if it encounters one of these
> "obsolete" setup.ini? Throw an error? Ignore the omission (how?)?
> Ignore the entire package entry?? Allow the user to continue anyway?
I'm afraid I'd have to test it to be sure, but I think that setup will
report a syntax error and attempt to continue processing the setup.ini file.
I suspect the package will not be in very useful state lacking version
or archive information.
--
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-05-08 19:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 11:11 Jon Turney
[not found] ` <CAG2dRtHsvRs-xTYN16Fw=OqUVAisQeMPFpppxV5E1pDsxMTVDg@mail.gmail.com>
2017-05-08 11:38 ` Dave Caswell via cygwin
2017-05-08 11:54 ` Jon Turney
2017-05-08 13:33 ` Henry S. Thompson
2017-05-08 17:37 ` Brian Inglis
2017-05-09 9:59 ` Jon Turney
2017-05-09 16:41 ` Brian Inglis
2017-05-09 19:37 ` Andrey Repin
2017-05-11 21:16 ` Jim Reisert AD1C
2017-05-08 11:49 ` Steven Penny via cygwin
2017-05-09 10:03 ` Jon Turney
2017-05-08 13:55 ` Eliot Moss
2017-05-09 11:22 ` Jon Turney
2017-05-09 13:37 ` Eliot Moss
2017-05-08 16:27 ` Ian Lambert via cygwin
2017-05-15 1:46 ` Jon Turney
2017-05-08 19:53 ` Peter A. Castro
2017-05-08 21:55 ` Jon Turney [this message]
2017-05-27 9:12 ` setup release candidate - no problems noticed L A Walsh
2017-05-08 18:28 setup release candidate - please test Eric Fahlgren
[not found] <1287176650.1659138.1494862170535.ref@mail.yahoo.com>
2017-05-15 15:56 ` Ian Lambert via cygwin
2017-05-15 16:15 ` Jon Turney
[not found] <129322595.2045958.1494880943500.ref@mail.yahoo.com>
2017-05-15 21:11 ` Ian Lambert via cygwin
2017-05-15 21:55 ` Brian Inglis
2017-05-16 11:10 ` Jon Turney
[not found] ` <3BE560BC-84EF-4C6D-8131-85A652C7B18E@yahoo.com>
2017-05-16 14:44 ` Jon Turney
2017-05-17 20:24 ` Jon Turney
2017-05-26 14:40 ` Jon Turney
[not found] <1118622054.582575.1494947930554.ref@mail.yahoo.com>
2017-05-16 16:55 ` Ian Lambert via cygwin
2017-05-16 17:08 ` Brian Inglis
[not found] <229690283.739700.1494954490567.ref@mail.yahoo.com>
2017-05-16 17:22 ` Ian Lambert via cygwin
2017-05-17 6:18 ` Brian Inglis
[not found] <1680333473.595405.1495810914804.ref@mail.yahoo.com>
2017-05-26 17:06 ` Ian Lambert via cygwin
2017-05-26 19:35 ` Jon Turney
2017-05-26 20:34 ` Peter A. Castro
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=cf7b76a7-ba72-4cef-cb7c-bdc06fe96ac2@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=doctor@fruitbat.org \
/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).