From: Phil Sutter <phil@nwl.cc>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Arturo Borrero Gonzalez <arturo@netfilter.org>
Subject: Re: [PATCH] build: put xtables.conf in EXTRA_DIST
Date: Fri, 13 Jan 2023 12:47:30 +0100 [thread overview]
Message-ID: <Y8FE0vEvtZhY6LCv@orbyte.nwl.cc> (raw)
In-Reply-To: <20230112225517.31560-1-jengelh@inai.de>
Hi Jan,
On Thu, Jan 12, 2023 at 11:55:17PM +0100, Jan Engelhardt wrote:
> To make distcheck succeed, disting it is enough; it does not need
> to be installed.
Instead of preventing it from being installed, how about dropping it
altogether?
The last code using it was dropped by me three years ago, apparently
after decision at NFWS[1]. Pablo removed the standalone 'xtables-config'
utility back in 2015[2], yet I see a remaining xtables_config_main
prototype in xtables-multi.h which seems to have been missed back then.
>
> Fixes: v1.8.8-150-g3822a992
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>
> ---
> Makefile.am | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile.am b/Makefile.am
> index 451c3cb2..10198753 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -16,11 +16,11 @@ SUBDIRS += extensions
> # Depends on extensions/libext.a:
> SUBDIRS += iptables
>
> -EXTRA_DIST = autogen.sh iptables-test.py xlate-test.py
> +EXTRA_DIST = autogen.sh iptables-test.py xlate-test.py etc/xtables.conf
>
> if ENABLE_NFTABLES
> confdir = $(sysconfdir)
> -dist_conf_DATA = etc/ethertypes etc/xtables.conf
> +dist_conf_DATA = etc/ethertypes
> endif
While being at it, I wonder about ethertypes: At least on the distros I
run locally, the file is provided by other packages than iptables. Do we
still need it? (It was added by Arturo for parity with legacy ebtables
in [3].)
Thanks, Phil
[1] 06fd5e46d46f7 ("xtables: Drop support for /etc/xtables.conf")
[2] 7462e4aa757dc ("iptables-compat: Keep xtables-config and xtables-events out from tree")
[3] 3397fb3be98ff ("ebtables-compat: include /etc/ethertypes in tarball")
next prev parent reply other threads:[~2023-01-13 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 22:55 [PATCH] build: put xtables.conf in EXTRA_DIST Jan Engelhardt
2023-01-13 11:47 ` Phil Sutter [this message]
2023-01-13 21:24 ` Jan Engelhardt
2023-01-16 11:57 ` Pablo Neira Ayuso
2023-01-16 16:31 ` Arturo Borrero Gonzalez
2023-01-16 17:18 ` Jan Engelhardt
2023-01-17 15:50 ` Phil Sutter
2023-01-17 15:56 ` Pablo Neira Ayuso
2023-01-17 16:03 ` Phil Sutter
2023-01-17 16:04 ` Pablo Neira Ayuso
2023-01-18 7:27 ` Duncan Roe
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=Y8FE0vEvtZhY6LCv@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=arturo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 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.