Date: Thu, 10 Oct 1996 12:51:40 +0200 (MET DST)
From: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Reply-To: grendel AT ananke DOT amu DOT edu DOT pl
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Install thingy
In-Reply-To: <Pine.SUN.3.91.961009080556.8012B-100000@is>
Message-ID: <Pine.NEB.3.95.961010124836.27096F-100000@ananke.amu.edu.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 9 Oct 1996, Eli Zaretskii wrote:

>
>On Tue, 8 Oct 1996, Mark Habersack wrote:
>
>> the executable with PMode extender. This makes the program entirely
>> stand-alone. I imagine that it would run in concert with djverify, wouldn't
>> it?
>
>I think that the installation process should run `djverify' as its last 
>stage, to verify the installation.  It might also run `djverify' at the 
>beginning (or during) the installation, to gather necessary data about 
>the system (why duplicate the code?).
I though I'd run DJVERIFY in the beginning to see whether DJGPP is already
installed and, if so, use its log file to see what parts of DJGPP are in the
system. Also, install would serve as a kind of shell for DJVERIFY. In case
DJGPP is installed but improperly, install would advise the user on what to do
in more visual manner and possibly correct the problems itself.
And the idea about running DJVERIFY at the end is excellent!

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Decriminalised genocide provided door to door Belsens. Pandora's box of
 Holocausts gracefully cruising satellite infested heavens.
Waiting, the season of the button, the penultimate migration. Radioactive
 perfumes, for the fashionably, for the terminally insane, insane
Do you realise, do you realise, do you realise?
This world is totally FUGAZI!
_-_-_-_-_-_-_-_-_-_- http://ananke.amu.edu.pl/~grendel -_-_-_-_-_-_-_-_-_