From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Updated: setup (2.888)
Date: Tue, 20 Feb 2018 12:43:00 -0000 [thread overview]
Message-ID: <announce.a2b9ae7d-e31f-f00d-ba81-1d19ef69deb5@dronecode.org.uk> (raw)
A new version of Setup, release 2.888, has been uploaded to
https://cygwin.com/setup-x86.exe (32 bit version)
https://cygwin.com/setup-x86_64.exe (64 bit version)
Changes compared to 2.884:
User visible changes:
- In the package chooser, 'Current' is replaced by 'Best' (to more
accurately summarize what it does)
- Add 'Sync' as a choice, (which sets all packages to the version
available from the package repository, downgrading if necessary,
equivalent to the existing --force-current command line option).
- These are modified by a 'Test' check-box, which allows test packages
to be used.
- The "prereq" page showing dependencies which will be added is replaced
by "problems" page showing problems found by the dependency solver, with
default solutions.
- A "confirm" page is added showing all the changes which will be made.
Internal changes:
- Uses the libsolv dependency solver, rather than a home-made one.
- Add support for 'depends2: package (relation version) [...]', in a
version section in setup.ini
- Add support for 'obsoletes:' in setup.ini, likewise
- Add support for 'replace-versions:' in a package section setup.ini, to
indicate problematic versions.
Other:
- Query the user for action to take if a corrupt local file is found
- Validate package hash after download
- Any MessageBox shown during setup.ini parsing is now modal
A big 'thank you' to Ken Brown for all his work on this.
Please send bug reports, as usual, to the public mailing list cygwin AT
cygwin DOT com.
--
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
reply other threads:[~2018-02-20 12:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=announce.a2b9ae7d-e31f-f00d-ba81-1d19ef69deb5@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).