X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	"Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: ANNOUNCE: DJGPP V2.03 Refresh Beta
Date:	Tue, 18 Dec 2001 15:42:35
Organization:	Aspen Technology, Inc.
Lines:	28
Message-ID:	<3c1f63eb.sandmann@clio.rice.edu>
References:	<200112181536 DOT fBIFajg13078 AT delorie DOT com> <3C1F8F7D DOT F2F2476C AT yahoo DOT com>
NNTP-Posting-Host:	dcloan.hou.aspentech.com
X-Trace:	selma.aspentech.com 1008713059 3841 10.32.115.107 (18 Dec 2001 22:04:19 GMT)
X-Complaints-To:	postmaster AT aspentech DOT com
NNTP-Posting-Date:	18 Dec 2001 22:04:19 GMT
X-NewsEditor:	ED-1.5.8
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Wouldn't it make more sense to distribute it as DJGPP 2.04 and
> later release the "in-the-works" 2.04 as 2.05?  

DJ answered this one.  The refresh has no new functionality.
If you don't need any of the fixes listed, it's 2.03.  No
header files were changed.  An 80Kb source update is provided 
to update the library alone if you would prefer.

> I hate to see modified versions with no obvious markers.  It 
> makes checking things by binary identity impossible.

The identification strings inside the images have changed from
the original release.  The new release has stub string:

stub.asm built 12/11/01 01:38:01 by djasm

and libc identification:

DJGPP libc built Dec 11 2001 22:28:26 by gcc 2.8.1

The .ver files also include a note about being updated.

The current 2.03 library and binaries do not contain the string
2.03 anywhere in them.  They will have a stub date of 12/09/99
and a libc date of Jan 4 2000. 

We will probably update the stub signature to 2.04 for the 
2.04 release.

- Raw text -