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, 01 Dec 2011 13:02:38 +0000 [thread overview]
Message-ID: <1322744558.17484.126.camel@ted> (raw)
In-Reply-To: <CAP9ODKpnTxcRDJxZKe0bue4RDqydJ44TmEf0ukv43ATgBcDV7Q@mail.gmail.com>
On Thu, 2011-12-01 at 10:59 -0200, Otavio Salvador wrote:
> On Thu, Dec 1, 2011 at 10:37, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> On Thu, 2011-12-01 at 13:24 +0100, Martin Jansa wrote:
> > A while back I've proposed to make .bbappend without
> corresponding .bb
> > only big fat warning, but not fatal to parse. Now you cannot
> even build
> > eglibc if there is libdrm bbappend you don't care at all
> about..
>
>
> You can do this by setting:
>
> BB_DANGLINGAPPENDS_WARNONLY
>
>
> This is even worse; you end up with a package without the changes done
> on the bbappend and as most bbappend files do not change PR, adding it
> later won't force a package update.
Which is why its off by default. My point is you can do with Martin is
suggesting, its just not without its drawbacks.
Cheers,
Richard
next prev parent reply other threads:[~2011-12-01 13:09 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 [this message]
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
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=1322744558.17484.126.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