From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <pb@pbcl.net>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: appears to be inconsistency re: base-files between oe-core and meta-angstrom
Date: Thu, 29 Aug 2013 12:57:13 +0100 [thread overview]
Message-ID: <1377777433.32502.71.camel@ted> (raw)
In-Reply-To: <1377776979.28077.88.camel@phil-desktop.brightsign>
On Thu, 2013-08-29 at 12:49 +0100, Phil Blundell wrote:
> On Thu, 2013-08-29 at 07:37 -0400, Robert P. J. Day wrote:
> > distroless. i realize i *could* set a value for DISTRO, but it would
> > seem that i shouldn't have to in order to avoid a build error.
>
> Well, either you're using angstrom or you aren't. If you do want to use
> it then you ought to set DISTRO appropriately, and if you don't want to
> use it then you probably oughtn't to have the angstrom layer included at
> all.
>
> Trying to use the angstrom .bbappends and files with a different (or no)
> distro configuration will give you a set of metadata that's neither one
> thing nor the other and, even if you didn't get a build error, there's
> no guarantee that the resulting image would actually work.
I'm not sure I agree. Ideally layers should be includable without
turning on behaviour unless it is enabled. This is why we have things
like an array of OVERRIDES to chose from.
So I'd actually suggest this is a bug in the angstrom layer. There are
also other layers which probably have issues, maybe including meta-yocto
but we should fix them.
I'll go further and suggest that Yocto Project Compatible status might
depend on this in future (the current questions suggest it should be the
case already).
Cheers,
Richard
next prev parent reply other threads:[~2013-08-29 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 10:29 appears to be inconsistency re: base-files between oe-core and meta-angstrom Robert P. J. Day
2013-08-29 10:49 ` Martin Jansa
2013-08-29 11:00 ` Robert P. J. Day
2013-08-29 11:27 ` Martin Jansa
2013-08-29 11:37 ` Robert P. J. Day
2013-08-29 11:49 ` Phil Blundell
2013-08-29 11:56 ` Robert P. J. Day
2013-08-29 11:57 ` Richard Purdie [this message]
2013-08-29 16:14 ` Chris Larson
2013-08-30 12:21 ` Robert P. J. Day
2013-08-29 11:49 ` Martin Jansa
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=1377777433.32502.71.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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