From: akuster808 <akuster808@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: [meta-security][PATCH] layer conf: update to include meta-networking
Date: Mon, 02 Feb 2015 15:24:58 -0800 [thread overview]
Message-ID: <54D0074A.50903@gmail.com> (raw)
In-Reply-To: <4593095.TQ4VoJlUyp@peggleto-mobl5.ger.corp.intel.com>
layer index updated.
I will update README next.
thanks,
Armin
On 02/02/2015 10:31 AM, Paul Eggleton wrote:
> On Monday 02 February 2015 10:24:21 akuster808 wrote:
>> On 02/02/2015 08:31 AM, Paul Eggleton wrote:
>>> Can you please also update the OE layer index?
>>
>> Do I do that manually or is it picked up from the README?
>
> No, it needs to be done manually, I don't have anything to parse a README and
> extract dependencies at the moment.
>
>>> http://layers.openembedded.org/layerindex/branch/master/layer/meta-securit
>>> y/
>>>
>>> I added meta-perl and meta-oe this morning based on the meta-security
>>> README - the latter isn't represented in your LAYERDEPENDS value though,
>>> so all three places ought to be made consistent with whatever the actual
>>> set of requirements is.
>>>
>>> (If people are starting to use LAYERDEPENDS a bit more it might make sense
>>> for us to add some code to the layer index update script to try to update
>>> its dependency list based upon LAYERDEPENDS and BBFILE_COLLECTIONS; up to
>>> now it hasn't seen a huge amount of use hence I hadn't done that.)
>>
>> Is the idea to include all layers required including the cascaded ones?
>>
>> i.e: meta-networking requires mete-python, should I include that one too?
>
> No, no need to do that - just the direct dependencies is enough.
>
> Cheers,
> Paul
>
prev parent reply other threads:[~2015-02-02 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 15:35 [meta-security][PATCH] layer conf: update to include meta-networking Armin Kuster
2015-02-02 16:31 ` Paul Eggleton
2015-02-02 18:24 ` akuster808
2015-02-02 18:31 ` Paul Eggleton
2015-02-02 23:24 ` akuster808 [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=54D0074A.50903@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@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.