From: Kbwms AT aol DOT com
Message-ID: <364ad5e.2444e333@aol.com>
Date: Tue, 13 Apr 1999 14:13:07 EDT
Subject: Re: LBInstDJ
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
CC: djgpp-workers AT delorie DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 38
Reply-To: djgpp-workers AT delorie DOT com

Subj:	 Re: LBInstDJ
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
CC:	djgpp-workers AT delorie DOT com

Dear Eli Zaretskii,

On 04-13-99 at 03:04:06 EST you wrote:
>
>
> On Mon, 12 Apr 1999 Kbwms AT aol DOT com wrote:
>
>
> But this is exactly the challenge of writing a good installer: how do
> you _handle_ all these complexities in a reasonable way that makes
> most users happy.  If we think that this undertaking is too dangerous,
> let's just quit now and not make the situation worse.
>

So, if some users are unhappy, that's okay, is it?  I contend that if a
remote chance exists that something untoward will occur, it is best to
write a provisional set-up file (autoexec.bat or whatever) and let the
user decide the next course of action.  This course of action should be
based on guidelines that the good guys (djgpp-workers) provide when the
provisional set-up file is written.

The fact that some users either won't or can't read the instructions
is a challenge to be faced in another venue.


K.B. Williams