[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging Gzstream?

On Fri, May 21, 2010 at 04:00:56PM +0900, Charles Plessy wrote:
> Dear all,
> I am interested in a set of programs, the ‘BEDtools’, whose source includes a
> convenience copy of the gzstream library.
> http://bedtools.googlecode.com
> http://www.cs.unc.edu/Research/compgeom/gzstream/
> A quick apt-file search indicates that at least two other packages (CCed) may
> be using the gzstream library, k3d and freecad. So it seems that it would
> make sense to package the gzstream library separately.

It appears to be just a single file less than four pages long.  It does
nothing but translate zlib's API to C++ iostream API.  While generally
avoiding duplicated code is a very good idea, it doesn't have to be done
with any small snippet.  Heck, I've written three zlib wrappers myself (two
of them had bzip2 support as well), and it never came to me that it's a task
big enough to be worth a whole library.

But then, many other simple bindings like this one have packages of their own.

> But I notice that this library has not been updated since 2003, and obviously,
> if only two programs in Debian are using it, there may be a more suitable
> alternative, that would be worth suggesting to the authors of BEDtools.

Uhm, what for?  zlib's API doesn't change, iostream is set in stone by the
language standard.  This tiny library isn't stagnant, it's finished.  You
don't need to update code unless either of the APIs change, some new
features are needed or a bug is found.  

1KB		// Microsoft corollary to Hanlon's razor:
		//	Never attribute to stupidity what can be
		//	adequately explained by malice.

Reply to: