Subject: zlib vs. gzopenfull(3)
To: None <>
From: matthew green <>
List: tech-userlevel
Date: 04/26/2004 02:41:59
hi folks.

a couple of months ago when i switched us to my gzip(1) implementation
i also added two new interfaces to libz (gzopenfull(3) and gzdopenfull(3))
which were used to implement both saved name & saved time-stamp features.

i've recently commited changes that remove the use of these functions
from gzip(1).  (due to switching to the low-level gzio functions, i had
to implement the gzip header reading & writing myself.)

it seems cleanest to me to simply remove these functions from zlib again
without bumping the major number.  they were only ever used by gzip(1)
and really shouldn't stay in zlib(3).  bumping zlib(3)'s major to remove
them seems likely to cause pain.  i can't imagine any other program is
using these API's yet (and they shouldn't) so no one should actually

i'm fully aware it's "the wrong thing" but sans strong objections i plan
to simply remove these from zlib in a couple of days.  (the minor should
probably bump as well?)

i will, of course, have this changed (if made) pulled up to 2.0.