From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: setup 2.895 release candidate - please test
Date: Sun, 21 Oct 2018 16:12:00 -0000 [thread overview]
Message-ID: <726f32f6-9307-8754-2b67-4537530decb6@dronecode.org.uk> (raw)
A new setup release candidate is available at:
https://cygwin.com/setup/setup-2.895.x86_64.exe (64 bit version)
https://cygwin.com/setup/setup-2.895.x86.exe (32 bit version)
Please test and report any problems here.
This is not the place for setup feature requests.
Changes compared to 2.893:
- Drag setup into the 1990s, by replacing the custom-drawn package
chooser with a ListView common control.
-- Use standard UI elements to choose an action to take on a package or
category, rather than the weird UX of clicking to cycle around a list of
options of undisclosed length.
-- Behaviour change: previously, a category action only affected
packages which matched any name search filter applied. Now all packages
contained by the category are affected.
-- Category view now shows a count of packages in a category
-- Add long description as a tooltip for description
-- Package selection can now be done via keyboard (crudely)
- Add support for ZStandard compression for packages and .ini files
- Fix a new warning reported by gcc 8
- Avoid a potential crash when checking for cached packages
Addresses: https://cygwin.com/ml/cygwin/2018-10/msg00033.html
- Use pkgconfig for build prerequisite checking
- Fix log spam when package vendor is something other than "cygwin"
- Various cleanups
Thanks to Ken Brown and Achim Gratz.
--
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 reply other threads:[~2018-10-21 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 16:12 Jon Turney [this message]
2018-11-06 10:29 ` Marco Atzeri
2018-11-06 17:16 ` Marco Atzeri
2018-12-06 9:12 ` Marco Atzeri
2018-12-16 14:52 ` Jon Turney
2018-12-16 20:44 ` Wayne Davison
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=726f32f6-9307-8754-2b67-4537530decb6@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
/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).