From: Peter Rosin <peda@lysator.liu.se>
To: cygwin@cygwin.com
Subject: Re: Update CoreUtils
Date: Tue, 13 May 2014 13:09:00 -0000 [thread overview]
Message-ID: <53721437.4080408@lysator.liu.se> (raw)
In-Reply-To: <CAAXzdLWoSg2zuMdZuYwL+baXpYq-472i2Y3iqte4MVhQ4WtEdQ@mail.gmail.com>
On 2014-05-13 14:29, Steven Penny wrote:
> On Tue, May 13, 2014 at 12:56 AM, Christopher Faylor wrote:
>> Frankly, please give MSYS2 another try. We'd all appreciate it.
>
> Look at the facts:
>
> coreutils
> newer version released 2 years ago
>
> bash
> newer version released 3 years ago
>
> git
> newer version released 2 years ago
>
> These are major packages, not just "user X favorite package". Several people
> including myself have offered to update them, only to be met with "Sorry, I am
> maintainer not you. I will do it when I get time". It gets old after a while.
Now, I'm just a random user, but exactly because these are major packages, it's
good to have a maintainer that actually understands and fixes problems related
to Cygwin, instead of having a maintainer that just builds the latest version
and uploads it. Given that you seem to love MSYS2 so much, I can report that I
recently dealt with a \r-issue with MSYS2 bash. I'd rather have a maintainer
that insulates me from \r-issues and says "no" before they hit me, than have a
maintainer that don't understand why stripping every \r in sight isn't such a
good idea. (to be fair, I'm not 100% sure it was an issue with the official
MSYS2 bash or if it was some 3rd party patch on top of the official MSYS2 bash,
I don't run MSYS2 personally).
That said, I'd also love a bash update, but I'd rather have a working bash than
a new bash. Because it is a major package.
2 cents
Cheers,
Peter
--
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
next prev parent reply other threads:[~2014-05-13 12:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 16:42 Steven Penny
2014-05-11 19:10 ` Thomas Wolff
2014-05-12 14:57 ` Eric Blake
2014-05-12 14:53 ` Eric Blake
2014-05-12 22:01 ` Steven Penny
2014-05-13 8:29 ` Christopher Faylor
2014-05-13 12:46 ` Steven Penny
2014-05-13 13:09 ` Peter Rosin [this message]
2014-05-13 15:04 ` Steven Penny
2014-05-13 15:05 ` Christopher Faylor
2014-05-13 18:36 ` Steven Penny
2014-05-13 18:47 ` Chris J. Breisch
2014-05-13 18:52 ` Larry Hall (Cygwin)
2014-05-13 19:16 ` Eric Blake
2014-05-13 21:11 ` Steven Penny
2014-05-13 19:43 ` Christopher Faylor
2014-05-13 23:26 ` Christopher Faylor
2014-05-14 1:51 ` Steven Penny
2014-05-14 3:01 ` Christopher Faylor
2014-05-31 13:29 ` PolarStorm
2014-05-29 17:45 ` David Conrad
2014-05-29 17:48 ` Christopher Faylor
2014-05-29 23:41 ` Steven Penny
2014-05-30 1:23 ` Chris J. Breisch
2014-05-30 1:42 ` Steven Penny
2014-05-30 9:05 ` Christopher Faylor
2014-05-30 16:19 ` Chris J. Breisch
2014-05-13 13:31 ` Christopher Faylor
2014-05-13 14:52 ` Chris J. Breisch
2014-05-13 19:17 ` Christian Franke
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=53721437.4080408@lysator.liu.se \
--to=peda@lysator.liu.se \
--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).