From: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Per package /bin/sh selection
Date: Wed, 8 Apr 2020 14:44:44 +0200 [thread overview]
Message-ID: <5e8dc73c.XZK73a32GsY+WdmD%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <7a1ced9f-782d-65bf-b420-7cedfd529a56@gentoo.org>
Michael Orlitzky <mjo@gentoo.org> wrote:
> Thanks, this will be a PITA for a while (again). Another developer had
> patched /bin/dash so that it was effectively broken, to the point where
> ./configure scripts would decide on their own use bash instead (even if
> you set /bin/sh to point to dash). This "fixed" the errors, but meant
Are there no unit tests for dash?
When ever I change something in bosh, I run the unit tests to verify that I did
not introduce a bug. One of the unit tests is to run a configure and compare
the results with the results frm a reference shell.
BTW: Did you ever think about replacing dash by bosh?
Bosh has the advantage to support multi byte characters.
Jörg
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
next prev parent reply other threads:[~2020-04-08 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 15:13 [gentoo-user] Per package /bin/sh selection Alessandro Barbieri
2020-04-07 16:09 ` Michael Orlitzky
2020-04-07 18:48 ` Alessandro Barbieri
2020-04-07 18:54 ` Michael Orlitzky
2020-04-08 12:44 ` Joerg Schilling [this message]
2020-04-08 16:14 ` Mike Gilbert
2020-04-08 17:17 ` Joerg Schilling
2020-04-08 18:59 ` Mike Gilbert
2020-04-09 10:40 ` Joerg Schilling
2020-04-08 22:44 ` [gentoo-user] " Ian Zimmerman
2020-04-08 22:49 ` Michael Orlitzky
2020-04-11 2:29 ` Ian Zimmerman
2020-04-11 2:34 ` Michael Orlitzky
2020-04-07 22:26 ` [gentoo-user] " Mike Gilbert
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=5e8dc73c.XZK73a32GsY+WdmD%Joerg.Schilling@fokus.fraunhofer.de \
--to=joerg.schilling@fokus.fraunhofer.de \
--cc=gentoo-user@lists.gentoo.org \
/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