Mail Archives: djgpp/1997/10/08/11:10:05
On Wed, 8 Oct 1997, Christopher Croughton wrote:
> How about a list of bugs in the downloaded version? That wouldn't take much
> to update, just a list of all 'open' bugs in te current system, updated say
> once a month.
You mean, in a separate file? What are the chances that people don't
forget to download another non-essential file?
Anyway, it still calls for a volunteer to maintain such a list. For
starters, people will need to know who is that person, and make a point
of reporting the bugs to him/her. Right now, it's a mess: some people
post to c.o.m.d., others write to DJ or to me, still others submit to the
bug-tracking system and never tell anybody else, etc.
> Hmm, by a 'complete' release I would expect to mean the compiler as well,
> hence my confusion.
DJ has decided to separate the core DJGPP from the rest, so now DJGPP
releases are not necessarily synchronized with the compiler and the rest
of the GNU tools.
> Indeed. But isn't this partly because of trying to do all the patches
> at once? I would have thought that incremental releases, with a couple
> of easily-tested patches in each one, would be better. That's the way I'm
> used to releasing code in a multi-user project in my job.
I suspect that in your job (as me in mine) you don't have to ask your
wife whether you could spend several hours making an update...
The point is that it takes time anyway. Obviously, a lot of small patches
done separately will incur a lot of overhead. Whether it is easier to
install the patches one by one or all of them together, is a function of
your arrangements with your Powers That Be at home. It depends on the
personal circumstances of each one of us.
> Could someone send me all of the patches? I don't have facilities to pull
> each one off the web site individually into a file, then edit to extract
> them, but if you (plural) already have an alpha version then someone must
> have already done that.
DJ has done that, he is the one who put together that alpha. Just write
to him and ask him about it.
> And if, for each new patch, I got an email (with
> some standard subject so I could filter it) containing it then I could
> do such a system. (The actual format and protocol would need to be worked
> out, of course, so that it could be automated).
It is doable, no doubt. If you are telling that you are willing to try
to make it happen, then it is up to you to define the procedures for
reporting library bugs. Just coordinate with DJ and make the announcement.
Of course, if you want to discuss what is the best format and procedure,
before you decide, that is OK too.
- Raw text -