From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] oe-setup-builddir: remove unreachable code, update comments
Date: Tue, 24 May 2011 15:35:42 -0700 [thread overview]
Message-ID: <4DDC32BE.6030802@linux.intel.com> (raw)
In-Reply-To: <d65327722591ceae682f08ff28cae38f4d32267d.1306276122.git.dvhart@linux.intel.com>
On 05/24/2011 03:31 PM, Darren Hart wrote:
> From: Darren Hart <dvhart@linux.intel.com>
>
> The script forces TEMPLATECONF to be non-empty with:
>
> TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf}
>
> This ensures that OELOCALCONF and OELAYERSCONF will be non-empty as well. Remove
> all the empty checks for these variables.
>
> While this patch doesn't change behavior, all this code was unreachable, it does
> bring up a point of intent. It appears as though OE*CONF was intended to be
> configurable by the user via the environment, the code only allows for the user
> to set TEMPLATECONF. This means that in order to use something other than the
> sample default configs, the user must specify both a local.conf.sample and a
> bblayers.conf.sample in their TEMPLATECONF directory.
>
> Update the comments to correctly identify the required files as local.conf.sample
> and bblayers.conf.sample.
>
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> ---
> scripts/create-pull-request | 2 +-
> scripts/oe-setup-builddir | 32 +++++++++++++-------------------
> 2 files changed, 14 insertions(+), 20 deletions(-)
>
> diff --git a/scripts/create-pull-request b/scripts/create-pull-request
> index b808146..169b888 100755
> --- a/scripts/create-pull-request
> +++ b/scripts/create-pull-request
> @@ -24,7 +24,7 @@
> # submission to Open Embedded and The Yocto Project, as well as to
> # related projects and layers.
> #
> -
> +set -x
EEEK, sorry about that. I've removed this and re-pushed to the same
contrib/dvhart/build branch. The only file changed is
scripts/oe-setup-builddir.
Apologies.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-24 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 22:31 [PATCH 0/1] oe-setup-builddir: remove unreachable code, update comments Darren Hart
2011-05-24 22:31 ` [PATCH 1/1] " Darren Hart
2011-05-24 22:35 ` Darren Hart [this message]
2011-05-25 6:32 ` [PATCH 0/1] " Saul Wold
2011-05-25 17:58 ` Darren Hart
2011-05-25 21:49 ` Saul Wold
2011-05-25 22:38 ` Richard Purdie
2011-05-25 23:39 ` Darren Hart
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=4DDC32BE.6030802@linux.intel.com \
--to=dvhart@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox