public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: setup 2.906 release candidate - please test
Date: Wed, 17 Mar 2021 22:16:03 +0100	[thread overview]
Message-ID: <7f360b0f-7d3b-09d9-a084-bbbba35ab303@towo.net> (raw)
In-Reply-To: <0d8d39fd-0bf0-225a-6963-1fa94a2f5037@dronecode.org.uk>

Am 17.03.2021 um 21:02 schrieb Jon Turney:
>
> A new setup release candidate is available at:
>
>   https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
>   https://cygwin.com/setup/setup-2.906.x86.exe    (32 bit version)
>
> Please test, and report any problems here.
I feel the need to take this occasion to woe about the terrible UI of 
setup. Two years or more ago there was a major revision, sarcastically 
accompanied by the comment the UI would have been pushed forward to the 
90s. Before that, you could simply select a package by clicking one (!) 
checkbox. Since then, you have to open a popup, scroll to the latest 
version and click that. This multiplies the effort to do selections 
significantly and it's quite a nuisance.
>
> This is not the place for setup feature requests.
It's not a feature as it was much better before; it's a regression. Can 
we please get back a fast-usable interface?
Thomas

>
> Changes compared to 2.905:
>
> - If a selected site URL saved from the last run starts with 
> "http://", and an identical URL, except starting with "https://", is 
> in the current mirror list, migrate it from "http://" to "https://".
>
> - Propagate the value of the CYGWIN environment variable into 
> post-install and pre-remove scripts (Thanks to Michael Wild for this 
> patch).
>   Partially addresses: 
> https://cygwin.com/pipermail/cygwin/2020-August/245994.html
>
> - Warn about unknown package names used with '--packages' or 
> '--remove-packages' options.
>
> - Move (potentially localizable) installation progress and package 
> action strings to string table resource.
>
> - Fix new warnings and build issues with gcc 10.


  parent reply	other threads:[~2021-03-17 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 20:02 Jon Turney
2021-03-17 20:08 ` Jon Turney
2021-04-26 12:00   ` Jon Turney
2021-03-17 21:16 ` Thomas Wolff [this message]
2021-03-17 21:29   ` Ken Brown
2021-03-21  0:33 ` Brian Inglis
     [not found] <822157107.1286425.1616430946694.JavaMail.administrator@n5.nabble.com>
2021-03-25 19:11 ` Jon Turney
     [not found] <182029171.1352421.1616703758747.JavaMail.administrator@n5.nabble.com>
2021-04-01 15:53 ` 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=7f360b0f-7d3b-09d9-a084-bbbba35ab303@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-apps@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).