From: L A Walsh <cygwin@tlinx.org>
To: Jack S <mplistarchive@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Would it be possible to update the bash package?
Date: Fri, 05 Mar 2021 07:32:10 -0800 [thread overview]
Message-ID: <60424EFA.2070500@tlinx.org> (raw)
In-Reply-To: <CAN3V7BTsX0CBKKW11Pz0rtO=1fskeKabf5YG26FDqv+utoQnDQ@mail.gmail.com>
On 2021/03/03 16:40, Jack S wrote:
> On Sun, Feb 28, 2021 at 10:03 PM L A Walsh wrote:
>
> What features are you looking for in 5.0 that you need it?
>
>
> Bug fixes and security updates. Also I want to have version parity with
> my servers.
----
I don't recall any security vulnerabilities reported
in 4.3/4.4 that have been fixed, and there have been just as
many bugs introduced in 5.0 as fixed, as features and behaviors
changed.
Really I don't see a compelling reason there should be
any hurry to update. In my own testing, I've been unable to
build a version that doesn't crash/dump core on linux and don't
really think the 5.x series has had a thorough vetting such
that it would be regarded as being as stable as 4.3/4.4.
The 5.x series is still new and I'm thinking if
5.x is offered, it should stay on the beta channel for a few
more major releases. I certainly don't see 5.0 being more
Posix compatible than the 4.x series or more compatible with
existing shells. I'm not sure cygwin should strive to be on
the bleeding edge as it is designed to be a Posix compatible
solution -- not necessarily something with all the latest
bleeding edge versions.
It's not up to me what version ships with cygwin,
but if I wanted a newer version I'd build it myself and I'd
hope the bash maintainer for cygwin would upgrade to 5.x when
5.x is more mature, though I certainly see no problem and would
support 5.x being offered as in the beta/test channel for a
few releases. That seems like a perfect fit for a stable vs.
new structure.
But that's just my opinion at the time...
-l
next prev parent reply other threads:[~2021-03-05 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 2:06 Matt
2021-03-01 6:03 ` L A Walsh
2021-03-04 0:40 ` Jack S
2021-03-05 15:32 ` L A Walsh [this message]
2021-03-05 19:23 ` Christoph Reiter
2022-03-06 15:59 ` Zartaj Majeed
2022-03-07 14:30 ` Adam Dinwoodie
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=60424EFA.2070500@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=mplistarchive@gmail.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).