public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Chris J. Breisch" <chris.ml@breisch.org>
To: cygwin@cygwin.com
Subject: Re: Update CoreUtils
Date: Tue, 13 May 2014 14:52:00 -0000	[thread overview]
Message-ID: <53722DE7.9060809@breisch.org> (raw)
In-Reply-To: <CAAXzdLWoSg2zuMdZuYwL+baXpYq-472i2Y3iqte4MVhQ4WtEdQ@mail.gmail.com>

Steven Penny wrote:
> 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.
>

Well, if you don't want to wait, and you're confident of your ability to 
update, then do so. You don't have to publish the package to use it on 
your own system.

I don't know anything about the git source, but I know that bash and 
coreutils are a pain to update, because there's so much in both that 
depends upon Windows text mode/binary mode annoyances. Also, bash (I 
believe) understands Windows paths, and that doesn't make porting any 
easier either. I spent a very brief time looking at updating bash 
myself, and decided it wasn't worth the pain.

I've done a little with coreutils in the past, and I suspect if I had 
to, I could update it using the patches from the last version as a 
starting point, but I haven't found a need to do so yet.

-- 
Chris J. Breisch

--
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

  parent reply	other threads:[~2014-05-13 14:36 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
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 [this message]
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=53722DE7.9060809@breisch.org \
    --to=chris.ml@breisch.org \
    --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).