From: Lee Dilkie <lee.dilkie@mitel.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1
Date: Fri, 24 Feb 2017 15:05:00 -0000 [thread overview]
Message-ID: <4a51815a-94c9-f97e-5be8-613ae67803ce@mitel.com> (raw)
In-Reply-To: <79698ed5-ac1d-99e3-c69c-c82b5dbc75e2@redhat.com>
On 2/24/2017 9:43 AM, Eric Blake wrote:
> On 02/23/2017 10:57 PM, Steven Penny wrote:
>>> Or more likely, many people likely have pre-existing scripts wrongly
>>> written as #!/bin/sh but which use bash-ism rather than portable
>>> POSIX-specified shell
>>
>> However, I think it is worth the trouble.
>
> If you'd like, I can post experimental versions of both bash and dash,
> which MUST be upgraded (or downgraded) in lockstep, where I move /bin/sh
> over to the dash package (do it wrong, and you could be left with no
> /bin/sh at all, which is not a good idea - although maybe I can use some
> postinstall scripts so that at least the upgrade side tries to play nice
> even when someone only does a partial upgrade). If people will then
> test with those experimental versions installed, and report breakage, we
> could get a feel for how many scripts installed by default are broken.
>
> But we are severely limited in volunteer manpower compared to Debian,
> and I suspect that 1) there won't be enough testers (we won't know the
> real impact until it is no longer experimental, but that is too late),
> and 2) even if testers are diligent, we will be unable to patch all the
> fallout in any sort of timely manner.
>
> Are you really prepared to force the Cygwin community through that much
> growing pain?
>
> I agree that /bin/sh as dash is much faster at executing configure
> scripts. But configure scripts aren't the only scripts in the wild. We
> do have checkbashisms ported to Cygwin, and that can help, but it is not
> a panacea.
>
If dash doesn't support all the features of bash (which is incorrectly assumed
in some cases for sh), aren't you just asking for trouble by breaking things?
-lee
--
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:[~2017-02-24 15:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 14:01 Eric Blake (cygwin)
2017-02-23 4:20 ` Steven Penny
2017-02-23 17:50 ` Andrey Repin
2017-02-23 19:46 ` Steven Penny
2017-02-23 19:59 ` Brian Inglis
2017-02-23 20:41 ` Eric Blake
2017-02-24 7:19 ` Yaakov Selkowitz
2017-02-23 23:44 ` Steven Penny
2017-02-24 14:32 ` Eric Blake
2017-02-24 19:19 ` Brian Inglis
2017-02-23 22:05 ` Andrey Repin
2017-02-23 23:01 ` Tony Kelman
2017-02-23 23:04 ` Eliot Moss
2017-02-23 23:12 ` Kenneth Wolcott
2017-02-23 23:30 ` Vince Rice
2017-02-23 23:35 ` Andrey Repin
2017-02-24 3:16 ` Larry Hall (Cygwin)
2017-02-24 3:18 ` Larry Hall (Cygwin)
2017-02-24 4:57 ` Steven Penny
2017-02-24 14:43 ` Eric Blake
2017-02-24 15:05 ` Lee Dilkie [this message]
2017-02-25 16:55 ` Steven Penny
2017-03-01 23:57 ` Matt Seitz (matseitz)
2017-02-23 23:33 ` Steven Penny
2017-02-25 16:46 ` cyg Simple
2017-02-25 17:09 ` Steven Penny
2017-02-27 10:20 ` Csaba Raduly
2017-02-27 12:48 ` Steven Penny
2017-02-27 23:13 ` Duncan Roe
2017-02-28 0:51 ` Steven Penny
2017-02-28 20:52 ` cyg Simple
2017-02-28 21:43 ` Steven Penny
2017-03-01 14:42 ` cyg Simple
2017-03-02 0:22 ` Steven Penny
2017-03-02 3:46 ` Vince Rice
2017-03-02 5:27 ` Steven Penny
2017-03-02 5:31 ` Vince Rice
2017-03-02 12:36 ` Steven Penny
2017-03-02 13:37 ` Marco Atzeri
2017-03-02 14:29 ` Eric Blake
2017-03-02 16:16 ` Nellis, Kenneth (Conduent)
2017-03-02 17:28 ` Brian Inglis
2017-03-02 18:45 ` Eric Blake
2017-03-02 23:23 ` Brian Inglis
2017-03-02 18:28 ` Achim Gratz
2017-03-02 14:31 ` Brian Inglis
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=4a51815a-94c9-f97e-5be8-613ae67803ce@mitel.com \
--to=lee.dilkie@mitel.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).