X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10112022025.AA14289@clio.rice.edu>
Subject:	Re: gzip-1.3.2 alpha port available for testing.
To:	djgpp-workers AT delorie DOT com
Date:	Sun, 2 Dec 2001 14:25:39 -0600 (CST)
Cc:	acottrel AT ihug DOT com DOT au (Andrew Cottrell),
	ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De (Juan Manuel Guerrero)
In-Reply-To:	<Pine.SUN.3.91.1011202105746.7623D-100000@is> from "Eli Zaretskii" at Dec 02, 2001 10:59:23 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> The patched libc 2.03 was not yet officially released.  I'm not sure it's 
> a good idea to base official ports on it, until Charles releases the 
> updated djdev203.zip.

Right now it's a matter of packaging and testing more than anything.
The current update kit allows you to update the libc.a and libdbg.a files
from a djdev203 and/or to update the source tree from djlsr203.  What I
have to do is find a few hours of time to extract a clean djlsr203,
update it, refresh the zip.  Do a make on it, refresh a djdev203.  Then
look at the cross files, etc and refresh them.  Put them someplace for
you guys to critque and test.

If the option is putting out new distributions based on djdev203 - use
the patch kit.  There are no new features - just bug fixes.

With that said, many simple packages won't change at all using the update.
Off hand, maybe only the "rename" bugs would be required fixes in something
like gzip.

- Raw text -