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.898)
Date: Sat, 28 Dec 2019 13:39:00 -0000	[thread overview]
Message-ID: <24bd8071-3ba1-30c1-ea51-cbdc672da568@dronecode.org.uk> (raw)


A new version of Setup (2.898) 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.897:

- '--upgrade-also' will now also upgrade an obsolete package specified 
on command line

(e.g.: setup -q -g -P python3-lxml currently gets you an (empty, 
obsolete) python3-lxml package, which is replaced by python36-lxml 
(which obsoletes it) the next time setup is run.  After this change, 
python36-lxml is installed instead)

(See also the discussion at 
https://cygwin.com/ml/cygwin-apps/2017-10/msg00092.html et seq. (where I 
come to the (incorrect) conclusion that since we don't need this for 
interactive use, it's not needed)

- Remove the 'Bin?' column

The only use this column now has is that unticking it is the same as 
selecting the 'uninstall' action.

- Packages can now depend with a version relation on the pseudo-package 
'_windows' (which has the same version as the Windows we are running on)

(This is intended for use with the cygwin package, to prevent updates 
being installed on Windows versions which it has dropped support for)


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

                 reply	other threads:[~2019-12-28 13:39 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=24bd8071-3ba1-30c1-ea51-cbdc672da568@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-announce@cygwin.com \
    --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).