From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: kaber@trash.net,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: build: do not install ip{,6}tables.h
Date: Tue, 29 Jul 2008 19:06:25 +0200 [thread overview]
Message-ID: <488F4E11.8020106@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0807291137150.21011@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Tuesday 2008-07-29 09:32, Pablo Neira Ayuso wrote:
>> I just realized that iproute may use this, however, it does not since it
>> keeps their own internal copy of the header files. Anyway, we should not
>> break the ABI because that would break iproute's ipt - actually, I
>> remember that such thing happened long time ago.
>> So, apart from your addon thing, I don't see any other client for the
>> xtables.h and you can also keep an internal copy of it.
>
> iproute's ipt has been discussed; patchesh ave been submitted by me,
> but it was not merged yet.
> More projects than just Xtables-addons can use xtables.h --
> xt_layer7 already compiles with it, ipt_ACCOUNT is just a blink away.
xtables.h also requires libiptc/libxtc.h which is, AFAIK, a header of
the internal iptables' library - not initially intended for external use.
Well, after all, it's ugly but it's not that bad as it only allows
people use the extension plugin API. I have committed your patch.
BTW, do we support C++ extensions for iptables? Hm, really?
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2008-07-29 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 22:51 build: do not install ip{,6}tables.h Jan Engelhardt
2008-07-29 11:57 ` Pablo Neira Ayuso
2008-07-29 13:32 ` Pablo Neira Ayuso
2008-07-29 15:50 ` Jan Engelhardt
2008-07-29 17:06 ` Pablo Neira Ayuso [this message]
2008-07-30 12:35 ` Jan Engelhardt
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=488F4E11.8020106@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--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.