nfq_set_verdict_mark

[Patrick McHardy]

Eric Leblond wrote:
> Le mercredi 11 octobre 2006 à 23:47 +0200, Pablo Neira Ayuso a écrit :
> 
> 
>>We can warn about incompatibilities in the announce of new releases for
>>this kind of minor issues that we need to fix up and that result in
>>breakages, some kind of "heads up" section.
> 
> 
> Why not to add a API release number in the code.
> 
> As developper of NuFW, I've got no problem to change my code but, I need
> a way to have my users not bored when they use my software. In fact I
> can not control which version of libnetfilter_queue.
> 
> Something like "#define NFQUEUE_API_VERSION NNN" in libnetfilter_queue.h
> could really be used easily in application code to detect which flavour
> of the API they need to use.

That doesn't really solve the problem of incompatibilities. Any breakage
is really bad for a supposedly stable library. Pablo's suggestion about
adding new functions without breaking the old ones makes sense of
course, but there is no guarantee that we won't fuck up again. Which is
why I wanted to raise the question whether we want to continue this
way or go back to beta state until we're reasonable sure about the API.

Well, for now I guess the best way is to add the new functions and
go through a really long beta phase with the new API (after releasing
the current versions, which contain quite a few bugfixes since the
last release).