Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] canutils: new recipe
Date: Fri, 7 May 2010 12:18:50 +0200	[thread overview]
Message-ID: <20100507101850.GD18308@excalibur.local> (raw)
In-Reply-To: <1272723767-16871-2-git-send-email-vjensen@gmx.de>

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?

> +RCONFLICTS = "socketcan-utils-test"
> +
> +TAG = "canutils-${PV}"
> +PR = "r0"
> +
> +SRC_URI = "git://git.pengutronix.de/git/tools/canutils.git;protocol=git;tag=${TAG} \
> +        "

Same about release tarballs and git SRC_URIs as from the other patch.

regards
Stefan Schmidt



  reply	other threads:[~2010-05-07 10:22 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 [this message]
2010-05-07 11:15         ` Koen Kooi
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=20100507101850.GD18308@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --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