From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Intel graphics driver community testing & development
<intel-gfx@lists.freedesktop.org>
Cc: chs@netbsd.org, Thomas Wood <thomas.wood@intel.com>,
riastradh@netbsd.org
Subject: Re: [RFC i-g-t] Deciding on #!/bin/bash or #!/bin/sh
Date: Fri, 9 Oct 2015 15:59:45 +0100 [thread overview]
Message-ID: <5617D661.6030702@linux.intel.com> (raw)
In-Reply-To: <1444399441.22306.4.camel@linux.intel.com>
On 09/10/15 15:04, Joonas Lahtinen wrote:
> Currently the shell scripts (+ a couple of 'execl') in intel-gpu-tools
> are are using a mix of #!/bin/bash (13) or #!/bin/sh shebangs (6). Also
> 5 of the #!/bin/bash scripts do source a #!/bin/sh script.
>
> I think we should have it unified, either drop Bash dependency
> completely or convert all scripts (and execl) to use it.
>
> Most of the scripts are not using any features at all that they would
> require a #!/bin/bash shebang or could not be trivially converted to be
> #!/bin/sh compliant. Most have actually been written with #!/bin/bash
> shebang but still with constructs like 'if [ "x${FOO}" = "x" ]' which
> basically are used for compatability with ancient shells. Explained at
> http://stackoverflow.com/a/6853353 .
>
> I'd say the bash shebang is there just because author wrote it by
> habit.
>
> In favor of #!/bin/bash there is the point made by Damien (CC'd) that
> it'll rule out the incoming bug reports that are due to alternative
> shell environments.
>
> In favor of #!/bin/sh NetBSD people (CC'd) informed they'll be glad to
> see bash requirement go.
>
> How about Android, does it make a difference there?
>
> My view on this is that converting everything to #!/bin/sh allows using
> BusyBox shell which makes the minimal testing build less complex. So
> I'm in favor of converting to #!/bin/sh.
I'll just mention "#!/usr/bin/env sh" as potentially more portable
option, for even more confusion. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-10-09 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:04 [RFC i-g-t] Deciding on #!/bin/bash or #!/bin/sh Joonas Lahtinen
2015-10-09 14:44 ` Morton, Derek J
2015-10-09 14:59 ` Tvrtko Ursulin [this message]
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=5617D661.6030702@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chs@netbsd.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=riastradh@netbsd.org \
--cc=thomas.wood@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.