Mail Archives: djgpp/1999/09/10/19:53:53
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in article
<Pine DOT SUN DOT 3 DOT 91 DOT 990909092342 DOT 6646N-100000 AT is>...
> And second, my experience in answering many questions from newbies
> here suggests that -lstdcx is NOT the single most frequent problem.
> It might seem so at times, but the long-term experience indicates
> otherwise. Documenting all those problems in a README would make it
> too long.
Indeed. But that's what I think READMEs are made for. For documenting
transient bugs and workarounds and other temporary stuff, to be easily and
quickly updated. Of course, basic installation instruction must be there too,
but everything else belongs to manual.
> You don't need anything except README.1ST, unless problems pop up.
> When they do, you should look in the FAQ for solutions. If the FAQ
> doesn't explain the solution, use the suggestions of section 6.15 of
> the FAQ to search the DJGPP archives, and if that doesn't help,
> section 6.16 tells you how to post questions here.
In fact I downloaded and browsed the FAQ even before downloading DJGPP itself
- just to know what am I getting into, being totally new to GNU tools.
> The FAQ is currently the de-facto Knowledge Base. The next DJGPP
> release adds some useful information to Knowledge Base, but it still
> won't be the repository of small tricks that you seem to want. The
> FAQ should fill that gap, at least for now.
Yes, but I still think that transient bug workarounds like this unfamous
RHIDE bug should somehow be separated from fundamental questions that aren't
likely to change with next minor version. Though, as you said in this thread
earlier, the Right Thing is fixing the bug, not describing it.
It seems to me that this particular RHIDE bug has one-line fix. I wonder does
nobody cared to mail RHIDE author about it? As I understand, this bug is
almost one year old and counting, as long as RHIDE 1.4 is recommended by DJ
zip-picker. Is it really that hard to add one file to distribution? Not that
I'm whining (or am I?), I just don't know the proper procedures. Allegro went
from 3.11 to 3.12 very quick, when the problem with building it with gcc-2.9
arised.
> Please feel free to make it better and submit the changes. I'm sure
> they will be gladly accepted.
Nah, my "personal itch" right now is to tweak RHIDE to make info browsing
more convenient. Trivial as it seems, for me it's big enough for now.
> The FAQ *is* this document. Most of it is about getting DJGPP to
> work, and work well. Simply use the indices, and you will see how
> effective it is in answering your questions.
BTW what are legal requirements on FAQ-derivated works? e.g. when writing my
own DJGPP reference, how can I use FAQ information in it?
- Raw text -