From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] oe-buildenv-internal: Only add to $PATH if needed
Date: Tue, 9 Apr 2013 17:14:26 -0500 [thread overview]
Message-ID: <516492C2.8030005@windriver.com> (raw)
In-Reply-To: <CAHUNapTSbxqXuj7LOsNSrZL5Ank+ngvkXF=cnhvM7aUK-DQZZA@mail.gmail.com>
On 4/9/13 12:29 PM, Trevor Woerner wrote:
> On Mon, Apr 8, 2013 at 1:48 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
>> Unfortunately I think this is specific to bash, so it may not be portable.
>> Maybe the equivalent can be achieved with sed however.
>
> Under which shells do we expect a Yocto build to succeed? The latest
> version of this change wouldn't work under tcsh, for example. (Not
> that I'm suggesting it should!) Isn't there already an inherent
> Bourne-ish expectation?
dash, ash, bash and zsh. POSIX compliant shells.
These are the places I try to verify scripts that refer to /bin/sh.
--Mark
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-04-09 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 16:59 [PATCH 0/3] Fixes for oe-init-build-env Peter Kjellerstedt
2013-04-05 16:59 ` [PATCH 1/3] oe-setup-builddir: Allow $OECORENOTESCONF to not exist Peter Kjellerstedt
2013-04-05 16:59 ` [PATCH 2/3] oe-buildenv-internal: Only add to $PATH if needed Peter Kjellerstedt
2013-04-08 17:31 ` Trevor Woerner
2013-04-08 17:48 ` Paul Eggleton
2013-04-08 22:40 ` Chris Larson
2013-04-09 10:01 ` Peter Kjellerstedt
2013-04-09 14:44 ` Chris Larson
2013-04-09 17:29 ` Trevor Woerner
2013-04-09 17:34 ` Trevor Woerner
2013-04-09 18:12 ` Paul Eggleton
2013-04-09 17:40 ` Khem Raj
2013-04-09 22:14 ` Mark Hatle [this message]
2013-04-05 16:59 ` [PATCH 3/3] oe-init-build-env: Make it use the correct $OEROOT with zsh Peter Kjellerstedt
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=516492C2.8030005@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 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.