From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Coordinating inter-layer dependencies
Date: Thu, 08 Dec 2011 00:17:37 +0000 [thread overview]
Message-ID: <1323303457.971.5.camel@ted> (raw)
In-Reply-To: <95547EE2-9E3E-4FB6-AA2A-A9653029F971@dominion.thruhere.net>
On Thu, 2011-12-01 at 12:23 +0100, Koen Kooi wrote:
> During the past month there have been a number of updates to OE-core
> recipes that triggered parsing errors due to bbappend in other layers.
> A small seleciton:
>
> * netbase
> * libdrm
> * xserver-xorg
> * clutter
>
> My view is that layer maintainers need to keep an eye on potential
> breakage and have updates ready when patches land into OE-core.
> Looking back I can see that while the situation is improving a bit,
> it's still not working. The problem with slow updates to layers is
> that (with my angstrom hat on) users (and with my TI hat on) customers
> and coworkers can't do builds without rm'ing the bbappends or
> disabling the layer.
I've been thinking about this. I wondered if the notion of wildcards
for .bbappend might help, e.g. a file called:
netbase_%.bbappend
would match all versions of the netbase recipe.
The % is consistent with PREFERRED_VERSION, I'm a little reluctant to
use * since its a shell quoting mess.
It wouldn't be hard to allow bitbake to support this and would solve
some of the issues we've been having...
Cheers,
Richard
next prev parent reply other threads:[~2011-12-08 0:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 11:23 Coordinating inter-layer dependencies Koen Kooi
2011-12-01 12:24 ` Martin Jansa
2011-12-01 12:37 ` Richard Purdie
2011-12-01 12:59 ` Otavio Salvador
2011-12-01 13:02 ` Richard Purdie
2011-12-01 13:13 ` Martin Jansa
2011-12-01 14:33 ` Chris Larson
2011-12-01 19:57 ` McClintock Matthew-B29882
2011-12-01 15:36 ` Koen Kooi
2011-12-01 15:56 ` Martin Jansa
2011-12-01 16:03 ` Koen Kooi
2011-12-01 13:07 ` Martin Jansa
2011-12-01 20:33 ` Richard Purdie
2011-12-02 8:46 ` Mats Kärrman
2011-12-02 13:34 ` Frans Meulenbroeks
2011-12-02 14:38 ` Otavio Salvador
2011-12-02 16:18 ` Martin Jansa
2011-12-02 16:22 ` [PATCH] bitbake.conf: add default PRINC 0 to be able to increment it Martin Jansa
2011-12-02 16:42 ` Richard Purdie
2011-12-02 18:39 ` [PATCHv2] " Martin Jansa
2011-12-02 19:29 ` Chris Larson
2011-12-05 16:09 ` Richard Purdie
2011-12-02 19:52 ` Coordinating inter-layer dependencies Chris Larson
2011-12-02 23:58 ` Mats Kärrman
2011-12-01 19:55 ` McClintock Matthew-B29882
2011-12-01 20:28 ` Chris Larson
2011-12-08 0:17 ` Richard Purdie [this message]
2011-12-08 21:07 ` McClintock Matthew-B29882
2011-12-10 0:51 ` Andreas Müller
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=1323303457.971.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox