X-Recipient: archive-cygwin AT delorie DOT 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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type; q=dns; s=default; b=f8uu wl3XHqWHLg2v5iDbOCTjmylL3jXt9CFr9cYuCHSJxYITQOF9B3ij/xdXLtqnFJR5 I6oNBLGBUG+DWLFcj6zaAKxor3/+w10uZfbcI+za+1cpmCuCjDgaFrDBH7Tc55Ir ThNJtg7xPnQo9RClduLX0zWzqYAq3Dx5samUXuE= 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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type; s=default; bh=IWYli25m5D 2HtcJhVX/dJedfh1o=; b=VveNfQObYCFnkXAk8AeD/Y+3Ju0FAN62XVFhYUZCmw oLQWKaMrjKR7H6CzT4Cyo1mhiqEhA/ZmfrxaEhdZgvN3xXoLZuPcoADRJanL9kjP GKqm2v29ckeXydBvJF9CmHzypfvsu7p3u8Z7Saqj82KHPp729Qo+Pz+KoBQzdPrX 8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=atzeri, Atzeri, tandem, WANT X-HELO: mx1.redhat.com Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1 To: cygwin AT cygwin DOT com References: <485AF0C5-7E1B-49AA-BE3E-C3717DA3268B AT solidrocksystems DOT com> <58b811b2 DOT 261d9d0a DOT 7c759 DOT 299d AT mx DOT google DOT com> From: Eric Blake Openpgp: url=http://people.redhat.com/eblake/eblake.gpg Message-ID: Date: Thu, 2 Mar 2017 08:29:01 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vANKSvGRjh38rTnlbApa7SSkD7ctxNaXF" X-IsSubscribed: yes --vANKSvGRjh38rTnlbApa7SSkD7ctxNaXF Content-Type: multipart/mixed; boundary="ie6V3lDEXKrJws9ovLnwUq2N6vOsD1chD"; protected-headers="v1" From: Eric Blake To: cygwin AT cygwin DOT com Message-ID: Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1 References: <485AF0C5-7E1B-49AA-BE3E-C3717DA3268B AT solidrocksystems DOT com> <58b811b2 DOT 261d9d0a DOT 7c759 DOT 299d AT mx DOT google DOT com> In-Reply-To: --ie6V3lDEXKrJws9ovLnwUq2N6vOsD1chD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 03/02/2017 07:36 AM, Marco Atzeri wrote: > On 02/03/2017 13:36, Steven Penny wrote: >> On Wed, 1 Mar 2017 23:31:24, Vince Rice wrote: >>> Then you haven't been paying attention. >>> And I didn't even attempt to make an argument one way or the other,=3D20 >>> except to say stop arguing. The horse is dead.=3D >> >> Perhaps you could link to a constructive, concrete idea against the >> change that >> someone has made besides Eric. Even better, you could post your own >> constructive >> idea; surely you havent emailed twice now with nothing constructive to >> add? >=20 > He was constructive, but you seems biased in understanding the answer. To reiterate my answer in different terms: If you can convince Fedora to switch /bin/sh to dash, then I will immediately follow in Cygwin. Until then, I'm worried that there are enough scripts in the wild that use bashisms and will therefore break if /bin/sh is not bash, even though that number has reduced somewhat since Debian made their switch. Trying to make Cygwin the guinea pig, instead of Fedora, is going about it backwards (you WANT the change to be done in a place where there is plenty of manpower to deal with the fallout, and Fedora has more manpower than Cygwin). I'm still toying with the idea of doing a test release of both bash and dash that flips /bin/sh between them; but I'm still stuck on the problem that a user MUST upgrade (or downgrade) both packages in tandem, or else risk being left without a /bin/sh at all. Help would be appreciated in figuring out the problem (telling me that "dash is faster than bash" is not help, nor is telling me that "portable shell scripts don't care if /bin/sh is bash or dash" - I already know those points. What I don't know is how many non-portable scripts are out there, so how much breakage would I be causing by forcing those non-portable scripts to deal with their non-portability, and how to minimize the even-worse breakage of an upgrade scenario that leaves no /bin/sh at all). Hmm, maybe I could create a NEW package, 'sh', which packages /bin/sh as however I want it (probably bash to begin with, to at least give people time to upgrade and pick up the packaging change before also having to deal with any shell changing). New releases of both bash and dash would depend on the new package, to guarantee that if you upgrade one shell, you pick up the dependency. And by not having /bin/sh in either the bash or dash package, then we would at least avoid the current situation where upgrading/downgrading in the wrong order could leave a user without /bin/sh at all. You might still be in a situation where the wrong version of the 'sh' package leaves you with an outdated version of a shell, or the wrong flavor in relation to the current distro choice, but that's less of a problem than having no /bin/sh at all. In fact, having a separate 'sh' package may make it even easier to pick which shell flavor you prefer (if I always keep the 'curr' and 'test' versions pointed to different shells, then you make the choice of which sh flavor you want by which version you install). --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --ie6V3lDEXKrJws9ovLnwUq2N6vOsD1chD-- --vANKSvGRjh38rTnlbApa7SSkD7ctxNaXF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJYuCwtAAoJEKeha0olJ0NqZVEH/iGKG1n0HkEITdXzIb0RPVcu ujRpN9H1faLwnnwEWX8n5Rme7jiS1X4P+pcIlOYquqyguVExsgCFAoJzKt6YSGvU YyTRksCNEnyYR5Z+kEHe7hiD1Nd9SkqFS91Uqe2cj7cLUbTD4J676I9wlPIVTmZN gzgiXosPQAc466Sm7FgluimLWULtrpHwVLVbkFRAS/iBGQ5/yOiioS/QC/DqRWZS PHrca0uysBDUQPGxlBkg8Nk0yEkd1ntIg7b6UJfyh8rvojExEgFXnZagb0yNmPNF snFjj1j5U/X3NO6ryo5nNWoeCEpQGZbv92aWyAWU1UA3wlRgLXIQO8gWW2zhyeo= =g8LJ -----END PGP SIGNATURE----- --vANKSvGRjh38rTnlbApa7SSkD7ctxNaXF--