Re: nfq_set_verdict_mark

[Eric Leblond <eric@inl.fr>]

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

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.

BR,
--
Regit


> 
> For the rest of the API, I remember that in one of my discussions with
> Harald we conclude that is better to introduce new API than breaking
> current just not to annoy users. We can strongly recommend the use of
> the new API and mark old one as deprecated (with the gcc attribute) to
> warn users that such obsolete function will vanish soon. That would
> stagger changes.
> 
> >> The current release process is too slow, I have the impression that
> >> nobody is using the lastest official releases. For conntrackd, I'm
> >> currently doing unnofficial releases of libnetfilter_conntrack because
> >> the official release is broken with NAT handlings, well apart from the
> >> fact that I also introduce some patches with new features that I need.
> > 
> > You're probably right (about people not using official releases) and
> > definitely right about releasing too seldom.
> > 
> >> Just tell you that I don't mind about spending some time on
> >> administration tasks like releases and any other stuff related with the
> >> website if that can help to speed up the release process. I worked on
> >> some scripts to automate the release process time ago after the workshop
> >> that I can recover.
> > 
> > That would be great. Let me know if you need anything (I think I recall
> > your keys expired?).
> 
> I need to renew my key in order to tag new releases in SVN, I also need
> to generate some kind of "release master GPG key" or something in other
> to sign new releases.
> 
-- 
Eric Leblond <eric@inl.fr>
INL

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 191 bytes --]