From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: indirect dependencies
Date: Wed, 17 Jun 2015 12:25:13 +0200 [thread overview]
Message-ID: <1434536714-22457-1-git-send-email-patrick.ohly@intel.com> (raw)
I recently ran into a situation where due to a stupid typo (DEPEND
instead of DEPENDS) my recipe happened to work for me when the
required package was pulled in indirectly and failed for someone else.
It would be nice if such indirect dependencies triggered a QA
warning, which they do not at the moment.
I started coding that, but ran into issues with false positives. I
don't have the time and knowledge to address these problems, but
wanted to shared the code anyway, in case that someone wants to
continue.
Patrick Ohly (1):
insane.bbclass: add indirect-build-deps QA check
meta/classes/insane.bbclass | 52 +++++++++++++++++++++++++++++++++++++++------
1 file changed, 45 insertions(+), 7 deletions(-)
--
2.1.4
next reply other threads:[~2015-06-17 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 10:25 Patrick Ohly [this message]
2015-06-17 10:25 ` [PATCH] insane.bbclass: add indirect-build-deps QA check Patrick Ohly
2015-06-17 11:52 ` Patrick Ohly
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=1434536714-22457-1-git-send-email-patrick.ohly@intel.com \
--to=patrick.ohly@intel.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