From: Patrick Ohly <patrick.ohly@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] cooker.py: allow dangling bbappends if explicitly whitelisted
Date: Fri, 02 Jun 2017 15:06:30 +0200 [thread overview]
Message-ID: <1496408790.30163.24.camel@intel.com> (raw)
In-Reply-To: <1496408295.6630.95.camel@linuxfoundation.org>
On Fri, 2017-06-02 at 13:58 +0100, Richard Purdie wrote:
> I'm wondering if there is a hybrid solution if we extend this syntax a
> little, e.g.:
>
> BBFILES_DYNAMIC += "\
> XXXX:${LAYERDIR}/optional-bbappends-XXX/recipes-*/*/*.bbappend
> YYYY:${LAYERDIR}/optional-bbappends-YYY/recipes-*/*/*.bbappend
> "
>
> so that the code only applies these BBFILES entries if the layer named
> in the first parameter is present?
>
> This would happen at the end of parsing so ordering becomes a moot
> point. The direction you stack BBFILES_DYANMIC in would determin
> bbappend application order.
>
> How does that sound to people?
Sounds good to me.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-06-02 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 10:50 [PATCH] cooker.py: allow dangling bbappends if explicitly whitelisted Patrick Ohly
2017-05-25 15:50 ` Christopher Larson
2017-05-25 20:01 ` Patrick Ohly
2017-05-26 13:56 ` Patrick Ohly
2017-05-30 19:54 ` Mark Hatle
2017-06-02 12:58 ` Richard Purdie
2017-06-02 13:06 ` Patrick Ohly [this message]
2017-06-02 13:26 ` Mark Hatle
2017-06-02 13:42 ` Christopher Larson
2017-06-02 16:14 ` Patrick Ohly
2017-06-02 16:20 ` Mark Hatle
2017-06-07 9:03 ` [PATCH] cookerdata: Add support for BBFILES_DYNAMIC Patrick Ohly
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=1496408790.30163.24.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.