www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1996/05/05/21:21:30

Date: Sun, 5 May 1996 21:20:36 -0400
From: dj (DJ Delorie)
Message-Id: <199605060120.VAA08949@delorie.com>
To: djgpp-workers
Subject: [rms AT gnu DOT ai DOT mit DOT edu: Re: [david AT thermoteknix DOT co DOT uk: RE: gcc/as/ld, COFF and embedding]]

Background: someone installed djgpp, had problems, sent e-mail to rms.
RMS thinks that the bug reporting mechanism isn't obvious enough.

Comments?  Yes, I know a big chunk of the conversation is missing.
I'm just interested in RMS's comment about the README files.

DJ


Date: Sun, 5 May 1996 20:01:54 -0400
From: Richard Stallman <rms AT gnu DOT ai DOT mit DOT edu>
To: dj AT delorie DOT com
In-reply-to: <199605051915 DOT PAA24660 AT delorie DOT com> (dj AT delorie DOT com)
Subject: Re: [david AT thermoteknix DOT co DOT uk: RE: gcc/as/ld, COFF and embedding]

    The individual zip files aren't expected to be treated independently;
    they won't work without a minimum set of base zip files installed.

Perhaps it would be a good idea for each zip file to come with a
README saying that.

I think he did install a sufficient collection of the zip files. but
he could not find the bug reporting info.  I think he did not know
where to look.

    Part of the base system is a very large frequently asked questions
    list (250K compressed), with an entire chapter on what to do if you
    encounter bugs (chapter 6).

Perhaps it would be good for each zip file to come with a README which
tells people where to find the FAQ and the bug reporting procedures.

Perhaps logically this should not be necessary, but it will make it
more reliable for users to find the info you want them to find.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019