From: Constantin Musca <constantinx.musca@intel.com>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] *** bblayers.conf should be updated automatically
Date: Wed, 26 Sep 2012 09:51:35 +0300 [thread overview]
Message-ID: <5062A5F7.7000003@intel.com> (raw)
In-Reply-To: <1348642178-27405-1-git-send-email-constantinx.musca@intel.com>
On 09/26/2012 09:49 AM, Constantin Musca wrote:
> To keep things simple for this release, Paul proposed to put the bblayers.conf
> merging code in sanity.bbclass. After upgrading bblayers.conf we tell the
> user to re-run. It would be better if we could re-read the configuration but that
> is something we can address in 1.4. Every layer should make its specific bblayers.conf
> updates by appending to the check_bblayers_conf bitbake function. We decided that this
> is the right thing to do because we don't want to be invasive. This represents the meta
> merging functionality and does only the bblayers.conf v4 -> v5 update. The v5 -> v6
> bblayers.conf update is done in another patch sent to poky@yoctoproject.org.
>
> Constantin Musca (1):
> sanity.bbclass: bblayers.conf should be updated automatically
>
> meta/classes/sanity.bbclass | 56 ++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 55 insertions(+), 1 deletion(-)
>
Sorry. Wrong mail list.
Constantin
next prev parent reply other threads:[~2012-09-26 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 6:49 [PATCH] *** bblayers.conf should be updated automatically Constantin Musca
2012-09-26 6:49 ` [PATCH] sanity.bbclass: " Constantin Musca
2012-09-26 6:51 ` Constantin Musca [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-26 6:52 [PATCH] *** " Constantin Musca
2012-09-26 6:52 Constantin Musca
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=5062A5F7.7000003@intel.com \
--to=constantinx.musca@intel.com \
--cc=bitbake-devel@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 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.