Date:	Tue, 7 Oct 1997 14:33:00 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Christopher Croughton <crough45 AT amc DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: Flaw in tmpfile() ?
In-Reply-To:	<97Oct6.173923gmt+0100.11649@internet01.amc.de>
Message-ID:	<Pine.SUN.3.91.971007143136.25685B-100000@is>
MIME-Version:	1.0

On Mon, 6 Oct 1997, Christopher Croughton wrote:

> > On Mon, 6 Oct 1997, Chris Croughton wrote:
> > 
> > > I don't know the mechanism for releasing new versions of the 
> > > library - perhaps I'm expected to put my recompiled version on 
> > > the web?
> > 
> > It's up to you.  The official corrected version will be in the next DJGPP 
> > release.
> 
> Which is when?

I don't know.  It's in the works and has seen its first alpha
version.

> Until then, you'll continue to get bug reports, and
> particularly because most people won't realise what's wrong for quite
> a time (and then are much more likely to suspect their own code than
> the library and waste even more time).

People who care about the quality of their libraries should watch
patches posted to this news group and visit the DJGPP bug-tracking
system (http://www.delorie.com/djgpp/bugs/) regularly.  If they
neglect doing this, it's tough on them, but I don't think you can
reasonably require more than these two services between releases.

> Can there not be a library release without having to do a complete DJGPP
> release?

A ``complete DJGPP release'' is nowadays nothing more than new libc.a,
libm.a and libdbg.a, new headers in include/ directory, and a
recompile of all the small DJGPP-specific utilities (such as `redir',
`symify' etc.).  It is still a lot of work to get all the libc
patches, install them, test them, make a few beta releases, get
responses from beta-testers and react on them, all of which needs to
be done before a release is ready.  It takes time, especially when
done by volunteers (DJ Delorie does most of this, btw) on their spare
time.

It would be nice if somebody (you?) would volunteer to maintain a site
where library patches (say, in the form of small zip files, one each
for every function patch) and/or an entire patched library could be
downloaded by people who need to patch their library quickly without
waiting for a release.  (If anybody is interested in such a project, I
can supply more details about what I think should be kept on such a
site.)

But until/unless somebody makes this happen, we are stuck with release
schedule that depends on the amount of free time DJ and other contributors
have available. 

- Raw text -