From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: IPT [PATCH] yay, autotools!
Date: Wed, 28 Nov 2007 12:58:23 +0100 [thread overview]
Message-ID: <474D57DF.1030002@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711281246420.16364@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Nov 28 2007 12:25, Patrick McHardy wrote:
>>>>> - I think we should move all manuals to libxt_*.man or perhaps
>>>>> even *.man, would reduce Makefile LOC.
>>>> You mean for the ones where we have an IPv4 and IPv6 version, but
>>>> no xtables extension? I'm not sure they're all similar ...
>>>>
>>> I mean libipt_unclean.man -> libxt_unclean.man. The source file
>>> libipt_unclean.c will persist. As unclean only matches libipt_%
>>> the manpage will only land in iptables.8, not ip6tables.8.
>> Then whats the advantage? Similar to the kernel, I think we should
>> only use xt_ for things that actually support more than one
>> address family.
>
> Well, just look at it:
>
> for ext in $(1); do \
> f="${srcdir}/libxt_$$ext.man"; \
> if [ -f "$$f" ]; then \
> echo ".SS $$ext"; \
> cat "$$f"; \
> continue; \
> fi; \
> f="${srcdir}/libipt_$$ext.man"; \
> if [ -f "$$f" ]; then \
> echo ".SS $$ext"; \
> cat "$$f"; \
> continue; \
> fi; \
> f="${srcdir}/libip6t_$$ext.man"; \
> if [ -f "$$f" ]; then \
> echo ".SS $$ext"; \
> cat "$$f"; \
> continue; \
> fi; \
> done >$@;
>
> could be reduced to 1/3 of its size.
size isn't everything :)
>>> BTW, libipq inside iptables seems to be totally unused, is it still needed?
>> Yes, people are still using it and the nfnetlink_queue compat library
>> is still nonfunctional.
>>
> but *iptables* itself does not use it, does it? in which case
> libipq should probably move to its own tarball, that is what
> I was proposing.
We could do that I guess, though I'm expecting a bunch of complaints
from people who are used to get it from the iptables source.
next prev parent reply other threads:[~2007-11-28 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 0:43 IPT [PATCH] yay, autotools! Jan Engelhardt
2007-11-28 1:21 ` Philip Craig
2007-11-28 8:48 ` Patrick McHardy
2007-11-28 11:09 ` Jan Engelhardt
2007-11-28 11:25 ` Patrick McHardy
2007-11-28 11:48 ` Jan Engelhardt
2007-11-28 11:58 ` Patrick McHardy [this message]
2007-11-28 12:05 ` Jan Engelhardt
2007-11-28 13:11 ` IPT [PATCH] autotools, number 2 Jan Engelhardt
2007-11-28 16:22 ` IPT [PATCH] yay, autotools! Laszlo Attila Toth
2007-11-29 7:48 ` Jozsef Kadlecsik
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=474D57DF.1030002@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.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.