From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] strongswan: add package
Date: Wed, 6 Mar 2013 09:21:32 +0100 [thread overview]
Message-ID: <20130306082132.GH7949@pengutronix.de> (raw)
In-Reply-To: <1362512222.4075.334.camel@mars>
On Tue, Mar 05, 2013 at 08:37:02PM +0100, Christoph Fritz wrote:
>
> Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> ---
> rules/strongswan.in | 10 ++++++++
> rules/strongswan.make | 62 +++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 72 insertions(+)
> create mode 100644 rules/strongswan.in
> create mode 100644 rules/strongswan.make
>
> diff --git a/rules/strongswan.in b/rules/strongswan.in
> new file mode 100644
> index 0000000..1e93801
> --- /dev/null
> +++ b/rules/strongswan.in
> @@ -0,0 +1,10 @@
> +## SECTION=networking
> +
> +config STRONGSWAN
> + bool
> + prompt "strongswan"
> + help
> + strongSwan is a complete IPsec implementation.
> + Please keep in mind to configure the kernel accordingly to fulfill
> + strongSwan's needs. See 'Required Kernel Modules' here:
> + http://wiki.strongswan.org/projects/strongswan/wiki/KernelModules
> diff --git a/rules/strongswan.make b/rules/strongswan.make
> new file mode 100644
> index 0000000..9c82672
> --- /dev/null
> +++ b/rules/strongswan.make
> @@ -0,0 +1,62 @@
> +# -*-makefile-*-
> +#
> +# Copyright (C) 2013 by Christoph Fritz <chf.fritz@googlemail.com>
> +#
> +#
> +# See CREDITS for details about who has contributed to this project.
> +#
> +# For further information about the PTXdist project and license conditions
> +# see the README file.
> +#
> +
> +#
> +# We provide this package
> +#
> +PACKAGES-$(PTXCONF_STRONGSWAN) += strongswan
> +
> +#
> +# Paths and names
> +#
> +STRONGSWAN_VERSION := 5.0.2
> +STRONGSWAN_MD5 := 77dc16443fd141f46183d3a4f60986ef
> +STRONGSWAN := strongswan-$(STRONGSWAN_VERSION)
> +STRONGSWAN_SUFFIX := tar.bz2
> +STRONGSWAN_URL := http://download.strongswan.org/$(STRONGSWAN).$(STRONGSWAN_SUFFIX)
> +STRONGSWAN_SOURCE := $(SRCDIR)/$(STRONGSWAN).$(STRONGSWAN_SUFFIX)
> +STRONGSWAN_DIR := $(BUILDDIR)/$(STRONGSWAN)
> +STRONGSWAN_LICENSE := GPL
> +
> +# ----------------------------------------------------------------------------
> +# Prepare
> +# ----------------------------------------------------------------------------
> +
> +STRONGSWAN_CONF_TOOL := autoconf
> +STRONGSWAN_CONF_OPT := \
> + $(CROSS_AUTOCONF_USR) \
> + --with-ipseclibdir=/usr/lib
I'm not sure if you misunderstood something, but I didn't mean that you
should remove the configure options.
You should explicitly specify all the options from the "Optional Features"
section from "./configure --help".
A good starting point usually is to add a kconfig options for all features
that have external dependencies (don't forget the 'select' in
strongswan.in) and choose a reasonable default for all others.
It's also a good idea to run "readelf -d <binary>" to check if you missed
any dependencies.
Michael
> +
> +# ----------------------------------------------------------------------------
> +# Target-Install
> +# ----------------------------------------------------------------------------
> +
> +$(STATEDIR)/strongswan.targetinstall:
> + @$(call targetinfo)
> +
> + @$(call install_init, strongswan)
> + @$(call install_fixup, strongswan,PRIORITY,optional)
> + @$(call install_fixup, strongswan,SECTION,base)
> + @$(call install_fixup, strongswan,AUTHOR,"Christoph Fritz <chf.fritz@googlemail.com>")
> + @$(call install_fixup, strongswan,DESCRIPTION,missing)
> +
> + @$(call install_tree, strongswan, 0, 0, $(STRONGSWAN_PKGDIR)/usr/sbin, /usr/sbin)
> + @$(call install_tree, strongswan, 0, 0, $(STRONGSWAN_PKGDIR)/usr/libexec, /usr/libexec)
> + @$(call install_tree, strongswan, 0, 0, $(STRONGSWAN_PKGDIR)/usr/lib, /usr/lib)
> + @$(call install_copy, strongswan, 0, 0, 0600, /etc/ipsec.d/private)
> + @$(call install_copy, strongswan, 0, 0, 0644, /etc/ipsec.d/certs)
> + @$(call install_copy, strongswan, 0, 0, 0644, /etc/ipsec.d/cacerts)
> +
> + @$(call install_finish, strongswan)
> +
> + @$(call touch)
> +
> +# vim: syntax=make
> --
> 1.7.10.4
>
>
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-03-06 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 21:22 [ptxdist] [PATCH] " Christoph Fritz
2013-03-04 17:04 ` Michael Olbrich
2013-03-05 19:37 ` [ptxdist] [PATCH v2] " Christoph Fritz
2013-03-06 8:21 ` Michael Olbrich [this message]
2013-03-06 10:10 ` Christoph Fritz
2013-03-06 12:50 ` Robert Schwebel
2013-03-06 22:54 ` [ptxdist] [PATCH v3] " Christoph Fritz
2013-03-20 11:44 ` Christoph Fritz
2013-03-20 13:49 ` Michael Olbrich
2013-03-26 11:21 ` [ptxdist] [PATCH v4] " Christoph Fritz
2013-03-27 18:10 ` Michael Olbrich
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=20130306082132.GH7949@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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