All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] layerindex.bbclass: Add ability to fetch layers from layer index
Date: Thu, 8 Jan 2015 17:18:08 +0800	[thread overview]
Message-ID: <54AE4B50.6010505@windriver.com> (raw)
In-Reply-To: <1458514.BbQ6jzxGvE@peggleto-mobl5.ger.corp.intel.com>


On 01/07/2015 05:20 PM, Paul Eggleton wrote:
> Hi Chong,
>
> On Wednesday 07 January 2015 14:35:42 Chong Lu wrote:
>> It maybe depends on other layers when one layer is added to BBLAYERS. If
>> define LAYERDEPENDS variable in this layer, we will get error from bitbake.
>> But sometimes, we don't have defined. Add a mechanism to fetch layers from
>> layer index and update bblayers.conf as appropriate. The layer index stores
>> dependencies of all layers. Query dependency from layer index and fetch
>> layer repo, then add this layer to BBLAYERS.
> Hmm, this is certainly interesting but not quite what I had in mind - I was
> thinking rather that bitbake-layers would be extended and it would be an
> explicit operation to add a layer from the layer index + all of its
> dependencies. We can of course also have something semi-automatic like this
> class, but the manual tool ought to come first IMHO (which the class could then
> make use of).
>
> Cheers,
> Paul

Hi Paul,

Thanks for your reply. I will try to extend bitbake-layers.

Best Regards
Chong

>



      reply	other threads:[~2015-01-08  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07  6:35 [PATCH 0/1] layerindex.bbclass: Add ability to fetch layers from layer index Chong Lu
2015-01-07  6:35 ` [PATCH 1/1] " Chong Lu
2015-01-07  9:20   ` Paul Eggleton
2015-01-08  9:18     ` Chong Lu [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=54AE4B50.6010505@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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.