All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dongxiao Xu <dongxiao.xu@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] meta-yocto: Define DISTRO in layer.conf
Date: Thu, 29 Mar 2012 14:23:08 +0100	[thread overview]
Message-ID: <1333027388.17502.2.camel@ted> (raw)
In-Reply-To: <eb5271caf52a62ab102078eb90fcd0482b74536e.1333022130.git.dongxiao.xu@intel.com>

On Thu, 2012-03-29 at 20:01 +0800, Dongxiao Xu wrote:
> Add the definition of DISTRO variable in meta-yocto/conf/layer.conf,
> and remove the corresponding definition in local.conf.sample.
> 
> As we know, if we source oe-init-build-env in Yocto project environment,
> we will have DISTRO="poky" set in local.conf by default, where the
> "poky" DISTRO comes from the meta-yocto layer. If user deletes
> meta-yocto layer from BBLAYERS in bblayers.conf, and then error will
> happen when bitbake parsing the local.conf, since it could not find
> where the "poky" DISTRO comes from.
> 
> Putting the DISTRO definition in layer.conf to avoid defining two
> related variables (DISTRO and BBLAYERS) in two separate
> configuration files (local.conf and bblayers.conf).
> 
> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
> ---
>  meta-yocto/conf/distro/poky.conf  |    1 -
>  meta-yocto/conf/layer.conf        |    1 +
>  meta-yocto/conf/local.conf.sample |    4 ++--
>  3 files changed, 3 insertions(+), 3 deletions(-)

I'm afraid this is the wrong approach. The UI should simply not allow
selection of a DISTRO option which is no longer available.

Setting DISTRO in local.conf is the way people expect to use the system
and we can't change that.

Cheers,

Richard



  reply	other threads:[~2012-03-29 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 12:01 [PATCH 0/1][PULL] layer.conf: Define DISTRO in layer.conf Dongxiao Xu
2012-03-29 12:01 ` [PATCH 1/1] meta-yocto: " Dongxiao Xu
2012-03-29 13:23   ` Richard Purdie [this message]
2012-03-29 13:39     ` Carl Simonson

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=1333027388.17502.2.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dongxiao.xu@intel.com \
    --cc=poky@yoctoproject.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.