HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]

Garrett Cooper yanefbsd at gmail.com
Fri Apr 2 21:32:31 UTC 2010

2010/4/2 Mark Linimon <linimon at lonesome.com>:
> On Thu, Apr 01, 2010 at 03:30:47PM +0200, Dag-Erling Smørgrav wrote:
>> And yes, I *will* keep harping on this until people Get It.
> You're harping at the wrong people.  Complain to the application authors,
> not to the poor slobs trying to maintain the ports collection.
> There's a lot of crap code out there on the internet.  If we want to
> insist that all the application authors both a) write good code and that
> b) understands how FreeBSD does things, well, we can do that, but it's
> not going to have much effect.
> Probably 75%+ of the application authors neither know nor care that
> their code is being run on anything other than Linux.  In extreme
> cases we've enountered authors who outright refuse to accept our
> patches, either due to philosophical disagreement or just due to the
> xtra hassle.

The problem actually was most likely the fact that the functionality
wasn't properly documented or that people didn't thoroughly read or
understand the documentation before implementing the feature. If
there's anything that I've learned from cleaning up messes in the past
(to be fair, some which I've created as well), it's that a lot of
incorrect logic is created by misunderstanding things and/or making
false assumptions on how things should work.

But yes, zlib is buggy w.r.t. the item Xin Li mentioned and needed to
be fixed. Too many folks try to resolve application porting issues by
using inline:

/* #define a constant or typedef a feature */

This generally quasi-works in versions A (assuming the application
runs and the developer upstream did their testing on version A's
software... heh) or version C (typically a Linux) developer decided
that they wanted to change the definition and dashed the consequences
about backwards compatibility in their code. kernel.org sources are
riddled with this kind of `decision making'.

But I digress...


More information about the freebsd-current mailing list