public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: Updated: setup (2.923)
Date: Sun, 20 Nov 2022 17:14:47 +0000	[thread overview]
Message-ID: <3b24439b-2b4e-b392-11f9-c3790b42c827@dronecode.org.uk> (raw)


A new version of Setup (2.923) has been uploaded to:

  https://cygwin.com/setup-x86_64.exe  (64 bit version)
  https://cygwin.com/setup-x86.exe     (32 bit version)

Changes compared to 2.919:

- Add perpetual support for preremove scripts (thanks to Christian Franke)

- Major update to libsolv (from 0.6.29 to 0.7.22).  Fix a crash this causes.

- Allow packages to be marked as 'self-destruct'.  (This is intended for 
use in the rare cases where a package is obsolete, but has no direct 
replacement.)

- Add new option '--no-write-registry', which inhibits recording the 
installation root directory in the registry, which may be useful for 
portable or temporary installs (thanks to Christian Franke)

- Add view modes "Removable" and "Unneeded" (thanks to Christian Franke)

- Add Ctrl-I/R/U as keyboard accelerators for 
install/reinstall/uninstall in the package chooser (thanks to Christian 
Franke)

- Restore the ability to run on Windows 5.1 (XP/Server 2003), in 
conjunction with '--allow-unsupported-windows'


This is not the place for setup feature requests.

For instructions on obtaining and building the source code for setup, 
see https://sourceware.org/cygwin-apps/setup.html

Please send bug reports, as usual, to the public mailing list cygwin AT 
cygwin DOT com.

             reply	other threads:[~2022-11-24 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 17:14 Jon Turney [this message]
2022-11-21 12:44 ` Jon Turney

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=3b24439b-2b4e-b392-11f9-c3790b42c827@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-announce@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).