All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/keepalived: add optional nftables dependency
Date: Sun, 24 Mar 2019 14:05:21 +0200	[thread overview]
Message-ID: <87h8bsmq9q.fsf@tarshish> (raw)
In-Reply-To: <20190324120016.28701-1-fontaine.fabrice@gmail.com>

Hi Fabrice,

On Sun, Mar 24 2019, Fabrice Fontaine wrote:
> nftables support has been added since version 2.0.11 and
> https://github.com/acassen/keepalived/commit/aa12175ea638912a7789e832634d7ccf80fdf48d
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/keepalived/keepalived.mk | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/package/keepalived/keepalived.mk b/package/keepalived/keepalived.mk
> index fcdb43ce13..d93f8be057 100644
> --- a/package/keepalived/keepalived.mk
> +++ b/package/keepalived/keepalived.mk
> @@ -46,4 +46,14 @@ else
>  KEEPALIVED_CONF_OPTS += --disable-libiptc
>  endif
>  
> +ifeq ($(BR2_PACKAGE_IPTABLES_NFTABLES),y)
> +KEEPALIVED_DEPENDENCIES += iptables
> +KEEPALIVED_CONF_OPTS += --enable-nftables

What do you need that for? Please explain in the commit log and in an
inline comment.

> +else ifeq ($(BR2_PACKAGE_NFTABLES),y)
> +KEEPALIVED_DEPENDENCIES += nftables
> +KEEPALIVED_CONF_OPTS += --enable-nftables
> +else
> +KEEPALIVED_CONF_OPTS += --disable-nftables
> +endif
> +
>  $(eval $(autotools-package))

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2019-03-24 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 12:00 [Buildroot] [PATCH 1/1] package/keepalived: add optional nftables dependency Fabrice Fontaine
2019-03-24 12:05 ` Baruch Siach [this message]
2019-03-25 17:54   ` Thomas Petazzoni
2019-03-25 18:22     ` Baruch Siach
2019-03-25 21:22       ` Arnout Vandecappelle
2019-03-27 17:45         ` Fabrice Fontaine

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=87h8bsmq9q.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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.