public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "/usr/bin/[" and coreutils
Date: Thu, 13 Oct 2011 16:30:34 +0200	[thread overview]
Message-ID: <20111013163034.78a57a1f@rohan.example.com> (raw)
In-Reply-To: <CA+czFiABDc6yh6=LBRn3n23b8VWBLDjTSfubX_a6=r1Nksku3A@mail.gmail.com>

On Thu, 13 Oct 2011 09:59:21 -0400
Michael Mol <mikemol@gmail.com> wrote:

> > The binaries are usually POSIX-compliant, whereas the builtins may
> > include extra bashisms (which tend to break apps expecting just
> > the basic POSIX behaviour)  
> 
> I haven't encountered POSIX-dependent apps breaking on bash, but I
> have encountered the reverse. My most annoying experience was when I
> tried building cinelerra on Debian a few years back. Cinelerra's
> script started with #!/bin/sh, but depended on bashisms--and I was
> running dash.

So you've also run into clueless devs and maintainers who know
almost nothing about shells?

Your example is an extreme one :-), but it's common enough to find
bashisms in scripts with an sh shebang 

-- 
Alan McKinnnon
alan.mckinnon@gmail.com



  reply	other threads:[~2011-10-13 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12  5:35 [gentoo-user] "/usr/bin/[" and coreutils William Kenworthy
2011-10-12  5:42 ` Canek Peláez Valdés
2011-10-12 16:49   ` Jonas de Buhr
2011-10-13 13:38     ` Jesús J. Guerrero Botella
2011-10-13 13:50       ` Alan McKinnon
2011-10-13 13:59         ` Michael Mol
2011-10-13 14:30           ` Alan McKinnon [this message]
2011-11-08  1:53             ` Claudio Roberto França Pereira
2011-11-08  6:01               ` Pandu Poluan
2011-11-08  6:03                 ` Pandu Poluan
2011-10-12  5:42 ` Manuel McLure
2011-10-12  5:45 ` meino.cramer
2011-10-12  6:04   ` William Kenworthy

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=20111013163034.78a57a1f@rohan.example.com \
    --to=alan.mckinnon@gmail.com \
    --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