On Fri, Dec 05, 2008 at 21:31:38 +0000, Duncan Coutts wrote: > > If this is not possible, we will just have to release darcs 2.2 without > > fixing the problem, and postpone zlib support till July. > > I think you should proceed on the basis that the api will not be > available for the immediate release and we'll try and have something > rock-solid in time for the July release.
Sounds like a plan! For the interested, this is basically just business as usual for darcs. The use of the zlib binding was originally intended to simplify building darcs on Windows (and also eventually to replace our own home-grown binding), but it is also much more stringent than our homegrown binding and has uncovered a bug in which our gzipped files would sometimes fail CRC checks. Our old binding ignores these CRC failures (which it should not), whereas the new external zlib binding throws an exception. The request to Duncan was for a more advanced zlib binding that would not only throw the exception, but include enough information for darcs to carry on and just warn the user instead of dying. Note that in any case, the bug which produces the broken CRCs has now been fixed. The issue at hand is really just how best to deal with pre-existing broken gzipped files. Since the new zlib will not be available, we will continue ignoring the error. In the July release, we will catch the error, and print a helpful warning, as per the plan that Ganesh discussed. Now the need to install libz has always made darcs a bit tricky to compile on Windows, but with Salvatore's help, I think we can publish a very simple HOWTO that helps Windows users to compile darcs. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpPAgIgc4Xjm.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
