Mail Archives: djgpp/1997/10/08/13:28:27
On Wed, 8 Oct 1997, Christopher Croughton wrote:
> > You mean, in a separate file? What are the chances that people don't
> > forget to download another non-essential file?
>
> No, I meant in the zip files you need to start (specifically in this case
> the library binary zip file - anyone who starts by downloading the library
> source before the binary isn't going to have much luck).
This means that djdev needs to be updated every month or so. Not very
nice.
> Do all bugs go into the tracking system eventually?
No. It depends on the person who reports it. DJ doesn't require the
bugs to go there, and doesn't update the tracker himself. He says the
bug-tracker is for users to see known bugs and solutions, but the burden
to maintain that database is on users also.
> If not, then there
> is a real problem (i.e. if bugs are being fixed without being tracked).
I think DJ checks the library against the bugs reporetd there sometime
into the update process.
> I don't know how the BTR is organised, but surely it must be possible to
> extract the bug reports from it in text format (or something convertable
> to text format, like TeX or HTML)?
It's HTML. Try asking DJ to let you have it in downloadable form
somewhere (the directory where the files are kept isn't readable by anon
ftp).
> I suspect there's some confusion about what exactly is 'DJGPP', then.
> I've always taken it to mean the entire system, comprising the compiler,
> libraries, and binutils,
That's how it was in the past, but DJ has decided there was no good
reason for this link, and it makes releasing a new version harder.
> But it shouldn't be just one person who has to do it, surely? Isn't it a
> distributed system, with several developers doing the work? Or does DJ
> have to do all the 'releasable' builds himself?
DJ does the most of work. It is very hard to do it any other way.
Somebody has to make sure everything works together, even if others
submit changes.
And sadly, there aren't too many ``others'' anyway. If anybody listens
out there, please come and help! Without enough volunteers to make DJGPP
better, this project isn't going anywhere!
> It seems he's the one who knows the bug tracking system, anyway. At very
> least, any bug which is entered into the tracking system should generate an
> email to the maintainers, preferably to a special list - from what I've seen
> of it djgpp-workers might be usable as a list for that purpose, or another
> list might be better. Perhaps this should be transferred to djgpp-workers
> anyway - thoughts?
djgpp-workers is a better forum, yes, but it doesn't replace actual
work. Somebody needs to do all those nice things that you are
describing.
- Raw text -