X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=YdYdiF
	1HKmb6TTWPiHZEWbgZU6AoLYev+igHbH/dS14AxHbmneXFIFM8Orz+po7hrltwbB
	FyYbp2wSey62MOr+HAGwraIxiJz30V65EEriY+HQsMbXm3QD4K145L2aZ2/djs9u
	Qwvi2t3ID+RkXvQSxJ4BU9cAtzM1sdM4oL5/g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; s=default; bh=n24J2ay4n7CC
	yFAFY/8cA2I7GiA=; b=JHLUEcy4MQfLJdimkSHfwahcm/zDj/HOKX6kDyuu2hnh
	ZFe+PTOBJsziQrfbkHNCjoMEeMS7H7ofSVdBXnUdU7ruPwRe98kuZPIMhhbvyPmR
	95Xoa1nN1jiKisDSN2WVyiuizsI66xdsHUZ0ZdaiNWxdFsMfHBItttw4lks0dBU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: mx1.redhat.com
Message-ID: <54D905CE.60108@redhat.com>
Date: Mon, 09 Feb 2015 12:09:02 -0700
From: Eric Blake <eblake@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: ca-legacy not bourne-compatible
References: <op.xtpmxk06ofd6j1@nebbiolo.upc.de> <mb8l3r$klv$1@ger.gmane.org> <54D8D634.7090201@redhat.com> <CACUHbYPfb_gkR8fhVuiVQ1DKgOT1Gus1VfDNvB70sSSr=O2C0w@mail.gmail.com>
In-Reply-To: <CACUHbYPfb_gkR8fhVuiVQ1DKgOT1Gus1VfDNvB70sSSr=O2C0w@mail.gmail.com>
OpenPGP: url=http://people.redhat.com/eblake/eblake.gpg
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GEd46jvXD0GTaqulkVxQdT3dLfwIvLq5n"
X-IsSubscribed: yes

--GEd46jvXD0GTaqulkVxQdT3dLfwIvLq5n
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 02/09/2015 11:25 AM, David Boyce wrote:
> On Mon, Feb 9, 2015 at 7:45 AM, Eric Blake <eblake@redhat.com> wrote:
>> For now, but I may move to dash someday in the future, like Debian did.
>=20
> By =E2=80=9CI=E2=80=9D are you referring to a personal decision at your s=
ite or do you
> mean you may exert your influence to get the default Cygwin /bin/sh
> switched to dash?

I mean that I package both bash and dash for cygwin, so it is fairly
easy for me as packager to make the switch for all users of future
cygwin downloads.  What is less easy is getting agreement on cygwin-apps
that it is the right time to make such a switch, as it may affect other
packages that don't realize they are shipping with non-sh-compatible
/bin/sh scripts (although thanks to Debian's efforts, this is a lot
better now than it used to be).  Don't worry, I wouldn't do it without a
reasonable lead-up time for experimental testing and appropriate
consensus.  But there ARE benefits to switching /bin/sh to dash: as it
loads fewer shared libraries and has less code bloat, it executes and
forks a lot faster, and since forking is noticeably slow on cygwin,
anything we can do to make non-interactive scripts faster is probably
worth it.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--GEd46jvXD0GTaqulkVxQdT3dLfwIvLq5n
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJU2QXOAAoJEKeha0olJ0NqNkwH/2eY+7y90FzIm4FBPD60kkCb
dup8yDZY7swYrTqTJ9aHaCAeVyjjUX0RcyABFCSF/PwEXht7R9ZhaJz7PpeGxaFY
boDHyKRVegBTTXNNJcu2jU7/MVMD9/5Vmp7URSKXo+ud+2o1j08gou82Y6wZyi/t
RDuZ7dxwn1y1vpc2S8b1TZUyQlv5hJ0ieiH2m1ukJf0cUy45BnojgGvApju3Viwt
HcQYx2cswxPDjC7r/622w4ZXH/y70Z76tutJkli2AGCsNfRIG9jyWUo9ybGDmhV1
Ur6C+osx5UTXfrsAH5uvZBJzCHU/N3kajCtuYyWOXjij6UzHiNbbVawWs1uCM9o=
=0dG/
-----END PGP SIGNATURE-----

--GEd46jvXD0GTaqulkVxQdT3dLfwIvLq5n--
