On Tuesday 2008-07-29 09:32, Pablo Neira Ayuso wrote:
>>>
>>> build: do not install ip{,6}tables.h
>>
>> Well, the same thing should apply for xtables.h. The iptables plugin API
>> has not been stable over the time. If we export that header file, we'll
>> have to get stuck to that API.
>The main point
>of the discussion is that neither this header nor any other in iptables
>- apart from libipq, of course - was designed to be exported.
xtables.h was exported *in the first place* to provide
this sort of API to other extensions.
>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.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
