delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/06/27/13:15:25

Newsgroups: comp.os.msdos.djgpp
From: manfred DOT heumann AT uni-bielefeld DOT de (Manni Heumann)
Subject: Re: can't get started
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990627180711 DOT 5761N-100000 AT is>
X-Newsreader: News Xpress 2.01
Date: Sun, 27 Jun 1999 16:11:06 GMT
NNTP-Posting-Host: ppp36-89.hrz.uni-bielefeld.de
Message-ID: <37764d1b.0@news.uni-bielefeld.de>
X-Trace: 27 Jun 1999 18:11:07 +0200, ppp36-89.hrz.uni-bielefeld.de
Lines: 30
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In article <Pine DOT SUN DOT 3 DOT 91 DOT 990627180711 DOT 5761N-100000 AT is>, djgpp AT delorie DOT com wrote:
>
>On Sat, 26 Jun 1999, Manni Heumann wrote:
>
>> Before this is getting even lengthier: Why don't you go ahead and write a 
>> little readme that does what you want?
>
>I'd bet that such a document will be an identical twin of README.1ST, 
>unless it leaves out several important issues.
>
>Hey, the DJGPP project is 10-year old.  Almost every complaint about 
>installation that can possibly be though of, has been already heard and 
>taken care of.

As always, Eli, you're right.

But how about this: Someone sits down and rights a little program, that will 
display the readme.1st. I'll be the first volunteer.
Then the same program does a little test with the reader. If he fails on a 
certain number of questions, it simply won't quit and once again display 
readme.1st.
If the reader gets his answers right the program will patch gcc. Before this 
patch, gcc will do nothing but spawn our little program.

Of course, I wasn't serious. But now that I think about it...

--

Manni

- Raw text -


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