----- Original Message -----
> Ken McDonell <kenj@xxxxxxxxxxxxxxxx> writes:
>
> > [...]
> > <rant>
> > probably because the developers of libmicrohttpd follow the open
> > source view (unlike the sgi irix 6.5 view) that breaking the API/ABI
> > is fine and to hell with backwards compatibility, which I'm guessing
> > prevents backporting to older distros and leaves them stuck with older
> > versions of the library
> > </rant>
>
> I really don't get the impression that this is the case with
> libmicrohttpd. While they don't go to the full ABI-compatibility sort
> of efforts related to symbol versioning etc., I am not aware of any
> API breakage over the time.
*nod*
> Instead of those folks, you might consider poking the debian packagers
> in question to see if they had considered moving to a newer version,
> and if not why. For that matter, why do they ship only pcp 3.3.3, or
> systemtap 1.2 for oldstable.
This isn't a Debian problem - Debian has long since moved on, and there
are many newer versions of Debian since this one. However, these older
platforms are still actively being used (evident from the fact we are
having this discussion :). Asking developers to release stable versions
more quickly doesn't help here (consider how far we might get trying to
get a RHEL4 microhttpd update, for example).
As a distributed, cross-platform toolkit it is actively in our interests
to support as many actively used platforms as we possibly can & evidently
some of these platforms (which Ken is telling us are still needed) are on
this older microhttpd, so it seems we need to find a way to support it.
cheers.
--
Nathan
|