Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH meta-oe v2 6/8] strongswan: add
Date: Fri, 16 Dec 2011 11:41:36 +0100	[thread overview]
Message-ID: <jcf790$99u$2@dough.gmane.org> (raw)
In-Reply-To: <1324028520-16474-6-git-send-email-b19537@freescale.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 16-12-11 10:41, b19537@freescale.com schreef:
> From: Zhenhua Luo <b19537@freescale.com>
> 
> strongSwan is an OpenSource IPsec implementation for the Linux operating
> system.
> 
> Signed-off-by: Zhenhua Luo <b19537@freescale.com> --- 
> .../recipes-support/strongswan/strongswan_4.5.1.bb |   21
> ++++++++++++++++++++ 1 files changed, 21 insertions(+), 0 deletions(-) 
> create mode 100644
> meta-oe/recipes-support/strongswan/strongswan_4.5.1.bb
> 
> diff --git a/meta-oe/recipes-support/strongswan/strongswan_4.5.1.bb
> b/meta-oe/recipes-support/strongswan/strongswan_4.5.1.bb new file mode
> 100644 index 0000000..9c5e736 --- /dev/null +++
> b/meta-oe/recipes-support/strongswan/strongswan_4.5.1.bb @@ -0,0 +1,21
> @@ +DESCRIPTION = "strongSwan is an OpenSource IPsec implementation for
> the \ +Linux operating system." +HOMEPAGE = "http://www.strongswan.org" 
> +SECTION = "console/network" +LICENSE = "GPLv2" +LIC_FILES_CHKSUM =
> "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3" + +SRC_URI =
> "http://download.strongswan.org/strongswan-${PV}.tar.bz2" 
> +SRC_URI[md5sum] = "81a4a699c4a1a49b74061dfa47b5a033" +SRC_URI[sha256sum]
> = "252d7369d94aa2d79e6fad078853b07ca897ea811ab1e1a2b008bcec0d1e758a" + 
> +EXTRA_OECONF = "--disable-curl --disable-soup --disable-ldap \ +
> --enable-gmp --disable-mysql --disable-sqlite \ +		--enable-openssl" + 
> +inherit autotools + +DEPENDS = "gmp openssl flex-native flex
> bison-native"

Normal DEPENDS go at the top :) Same for the rng-tools recipe. The general
idea is that 'recipe' variable go on top and other variables are ordered
next to the tasks they are used in, e.g. RDEPENDS are for do_packages, so
they go below do_install, DEPENDS are for the recipe, so they go on top.

> +RRECOMMENDS_${PN} = "kernel-module-ipsec" + +FILES_${PN}-dbg +=
> "${libexecdir}/ipsec/.debug ${libexecdir}/ipsec/plugins/.debug"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk7rIGAACgkQMkyGM64RGpHudwCgu3FhI+64lWnp7q6gzK1itDW3
2TYAn0lXYwRxN5vKcrErNyF4jZO8adfy
=Zmzb
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-12-16 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  9:41 [PATCH meta-oe v2 1/8] bridge-utils: add b19537
2011-12-16  9:41 ` [PATCH meta-oe v2 2/8] ietutils: add b19537
2011-12-16  9:41 ` [PATCH meta-oe v2 3/8] ipsec-tools: add b19537
2011-12-16  9:41 ` [PATCH meta-oe v2 4/8] libnfnetlink: add b19537
2011-12-16  9:41 ` [PATCH meta-oe v2 5/8] ptpd: add b19537
2011-12-16  9:41 ` [PATCH meta-oe v2 6/8] strongswan: add b19537
2011-12-16 10:41   ` Koen Kooi [this message]
2011-12-16 11:04     ` Luo Zhenhua-B19537
2011-12-16  9:41 ` [PATCH meta-oe v2 7/8] rng-tools: add b19537
2011-12-16  9:42 ` [PATCH meta-oe v2 8/8] xfsprogs: add b19537
2011-12-16 10:38 ` [PATCH meta-oe v2 1/8] bridge-utils: add Koen Kooi

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='jcf790$99u$2@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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