From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: mike.looijmans@topic.nl
Cc: OE <openembedded-core@lists.openembedded.org>
Subject: Re: What does "QA Issue: ... rdepends on .. but its not a build dependency?" mean
Date: Sun, 03 Aug 2014 14:51:24 +0100 [thread overview]
Message-ID: <53DE3E5C.5020303@dynamicdevices.co.uk> (raw)
In-Reply-To: <53DE3841.2000305@topic.nl>
On 03/08/2014 14:25, Mike Looijmans wrote:
> I'm getting lots of warnings like this:
>
> """
> WARNING: QA Issue: enigma2-plugin-systemplugins-wirelesslan rdepends
> on wireless-tools but its not a build dependency? [build-deps]
> """
>
> What does it actually mean? What does it want me to provide here?
>
> The message in itself is correct. The package only has a runtime
> dependency. It does not require the wireless-tools package to be built
> or otherwise present on the build system. But what is the QA issue
> here and how do I get rid of the message?
>
Surely if package B has a non-optional runtime dependency on package A
then package A must be built and present on the target ?
> Apart from that, there's a spelling error in there (its -> it's)
> because it's "it's" when it's "it is" and it's "its" when it's its
> property.
>
It is a spelling error in a superficial sense perhaps, but at a deeper
level I suspect it is more accurately characterised as a grammatical error.
Perhaps somebody was having trouble with string terminations and decided
to avoid trouble?
Cheers,
Alex
next prev parent reply other threads:[~2014-08-03 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 13:25 What does "QA Issue: ... rdepends on .. but its not a build dependency?" mean Mike Looijmans
2014-08-03 13:51 ` Alex J Lennon [this message]
2014-08-03 14:02 ` Mike Looijmans
2014-08-03 16:16 ` Richard Purdie
2014-08-03 19:23 ` Alex J Lennon
2014-08-03 16:07 ` Richard Purdie
2014-08-03 17:35 ` Mike Looijmans
2014-08-03 17:48 ` Mike Looijmans
2014-08-04 5:12 ` Mike Looijmans
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=53DE3E5C.5020303@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=mike.looijmans@topic.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.