From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mikhail Durnev <Mikhail_Durnev@mentor.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: classes/insane: add check for PN in OVERRIDES
Date: Wed, 28 Aug 2013 09:41:19 +0100 [thread overview]
Message-ID: <3236564.Bbn6H3DI5P@helios> (raw)
In-Reply-To: <521C48D3.3010901@mentor.com>
Hi Mikhail,
On Tuesday 27 August 2013 17:36:03 Mikhail Durnev wrote:
> I have a question about your commit c331f0a:
>
> -------------------------------------------
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index 4d2392e..fb18022 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -907,6 +907,11 @@ python () {
> if d.getVar('do_stage', True) is not None:
> bb.fatal("Legacy staging found for %s as it has a do_stage
> function. This will need conversion to a do_install or often simply
> removal to work with OE-core" % d.getVar("FILE", True))
>
> + overrides = d.getVar('OVERRIDES', True).split(':')
> + pn = d.getVar('PN', True)
> + if pn in overrides:
> + bb.warn('Recipe %s has PN of "%s" which is in OVERRIDES, this
> can result in unexpected behaviour.' % (d.getVar("FILE", True), pn))
> +
> issues = []
> if (d.getVar('PACKAGES', True) or "").split():
> for var in 'RDEPENDS', 'RRECOMMENDS', 'RSUGGESTS',
> 'RCONFLICTS', 'RPROVIDES', 'RREPLACES', 'FILES', 'pkg_preinst',
> 'pkg_postinst', 'pkg_prerm', 'pkg_postrm', 'ALLOW_EMPTY':
> ----------------------------------------------
>
> A recipe (lets say linux_git.bb) has its PN in OVERRIDES with prefix
> 'pn-' (pn-linux). So, if we have 'linux' in OVERRIDES then it cannot
> interfere.
Unfortunately that is not the case. If PN is "linux" and TARGET_OS is "linux"
(note, for ARM machines only TARGET_OS may be "linux-gnueabi" rather than
"linux") then statements such as this:
FILES_${PN} = "/path/to/file"
will immediately become:
FILES = "/path/to/file"
Which itself will trigger a warning about FILES not being package specific.
Without an explicit check on PN being in OVERRIDES it's not immediately
obvious what has happened.
Additionally consider the following case in local.conf:
PREFERRED_VERSION_linux = "3.8.10"
This will turn into PREFERRED_VERSION = "3.8.10" and then you'll get a bunch
of spewed notices about version "3.8.10" being unavailable for every recipe in
the system that you're building.
PN in OVERRIDES is bad news, which is why we added this warning. You really do
need to name your recipes so that they don't clash with items in OVERRIDES.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-28 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 6:36 classes/insane: add check for PN in OVERRIDES Mikhail Durnev
2013-08-28 8:41 ` Paul Eggleton [this message]
2013-08-28 10:54 ` Mikhail Durnev
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=3236564.Bbn6H3DI5P@helios \
--to=paul.eggleton@linux.intel.com \
--cc=Mikhail_Durnev@mentor.com \
--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