From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] canutils: new recipe
Date: Fri, 07 May 2010 13:15:02 +0200 [thread overview]
Message-ID: <hs0snm$i4a$1@dough.gmane.org> (raw)
In-Reply-To: <20100507101850.GD18308@excalibur.local>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-05-10 12:18, Stefan Schmidt wrote:
> Hello.
>
> On Sat, 2010-05-01 at 16:22, Vitus Jensen wrote:
>> Adds canutils (PTX flavour) 4.0.4 as alternative to socketcan-utils-test.
>> canutils RCONFLICTS with socketcan-utils-test because of identical
>> file names.
>>
>> Signed-off-by: Vitus Jensen <vjensen@gmx.de>
>> ---
>> recipes/socketcan/canutils_4.0.4.bb | 19 +++++++++++++++++++
>> recipes/socketcan/socketcan-utils-test_svn.bb | 1 +
>> 2 files changed, 20 insertions(+), 0 deletions(-)
>> create mode 100644 recipes/socketcan/canutils_4.0.4.bb
>>
>> diff --git a/recipes/socketcan/canutils_4.0.4.bb b/recipes/socketcan/canutils_4.0.4.bb
>> new file mode 100644
>> index 0000000..e769c46
>> --- /dev/null
>> +++ b/recipes/socketcan/canutils_4.0.4.bb
>> @@ -0,0 +1,19 @@
>> +DESCRIPTION = "canutils (PTX flavour)"
>> +AUTHOR = "Luotao Fu"
>> +HOMEPAGE = "http://www.pengutronix.de"
>> +SECTION = "console/network"
>> +PRIORITY = "optional"
>> +LICENSE = "LGPL"
>> +DEPENDS = "libsocketcan"
>> +RDEPENDS = "libsocketcan"
>
> Why do you need this RDEPENDS on the lib when it is already in DEPENDS?
The better question is "Why doesn't OE shlib code pickup that
dependency?" :)
Regardless of that, RDEPENDS = "foo" is bad, RDEPENDS_${PN} = "foo" is
better. Chris created the recipe sanity stuff to check for these kinds
of things.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL4/Y2MkyGM64RGpERApiGAKCHkZaERI3RjRMFni0srqrz1bK1zACgh4Oc
txgZHww4OIZWD+cvr+GWb5w=
=eDEU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-07 11:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 17:14 canutils Vitus Jensen
2010-04-16 17:15 ` [PATCH 1/2] libsocketcan: recipe to build pengutronix' libsocketcan (netlink interface) Vitus Jensen
2010-04-16 17:31 ` Koen Kooi
2010-04-16 19:28 ` Vitus Jensen
2010-04-16 20:35 ` Henning Heinold
2010-04-20 8:09 ` Vitus Jensen
2010-04-16 17:16 ` [PATCH 2/2] canutils: add new recipe Vitus Jensen
2010-04-19 14:34 ` canutils Vitus Jensen
2010-04-19 14:34 ` [PATCH] angstrom-2008: make PREFERRED_VERSION_linux-libc-headers a weak assignment Vitus Jensen
2010-04-19 20:01 ` Koen Kooi
2010-04-20 6:32 ` Vitus Jensen
2010-04-29 17:04 ` GNUtoo
2010-05-01 14:17 ` canutils Vitus Jensen
2010-05-01 14:22 ` [PATCH v2] libsocketcan: new recipe Vitus Jensen
2010-05-01 14:22 ` [PATCH v2] canutils: " Vitus Jensen
2010-05-07 10:18 ` Stefan Schmidt
2010-05-07 11:15 ` Koen Kooi [this message]
2010-05-16 20:26 ` Vitus Jensen
2010-05-21 14:38 ` [PATCH v3 1/3] libsocketcan: new recipes Vitus Jensen
2010-05-21 14:38 ` [PATCH v3 2/3] canutils: " Vitus Jensen
2010-05-21 14:38 ` [PATCH v3 3/3] socketcan-utils-test: rconflicts with canutils Vitus Jensen
2010-05-21 20:39 ` [PATCH v3 1/3] libsocketcan: new recipes Khem Raj
2010-05-22 15:26 ` Vitus Jensen
2010-05-07 10:17 ` [PATCH v2] libsocketcan: new recipe Stefan Schmidt
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='hs0snm$i4a$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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