From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: can i blacklist a particular .bbclass file when there are more than one?
Date: Thu, 30 Apr 2020 09:49:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2004300945580.19276@localhost.localdomain> (raw)
given an odd collection of layers wherein there are multiple
instances of a particular .bbclass file, it turns out that all of the
recipes i'm interested in build with an older version of the class
file, and all but one build consulting the newer form of the file
contained in another layer, so is there any way to blacklist a
particular class file, either globally or even on a per-recipe basis?
i realize this is really, really bad design style, but it will give
me the chance to use the proper class file for most of the recipes
while i debug the problematic recipe.
rday
next reply other threads:[~2020-04-30 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 13:49 Robert P. J. Day [this message]
2020-04-30 17:01 ` [OE-core] can i blacklist a particular .bbclass file when there are more than one? Denys Dmytriyenko
2020-05-04 8:38 ` Quentin Schulz
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=alpine.LFD.2.21.2004300945580.19276@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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