Message-ID: <325CAF3C.3F55@cs.com>
Date: Thu, 10 Oct 1996 01:09:32 -0700
From: "John M. Aldrich" <fighteer AT cs DOT com>
Reply-To: fighteer AT cs DOT com
Organization: Three pounds of chaos and a pinch of salt
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>, djgpp-workers AT delorie DOT com
Subject: Re: Install thingy
References: <Pine DOT SUN DOT 3 DOT 91 DOT 961009080556 DOT 8012B-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Eli Zaretskii wrote:
> 
> 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?).

Well, the final djverify will be designed to be run at any stage of the
process:  before you install anything, during the installation, or after
you've installed.  Also, unless it works by returning error codes to the
installer, I don't see how the latter would be able to properly
interpret what djverify reports.  Hmm... it's an interesting question. 
Mark, if you'd like to work on coordinating with djverify so we can work
something like that out, I'd be more than happy to help.  :)

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I |        fighteer AT cs DOT com          |
| Proud owner of what might one   |   http://www.cs.com/fighteer    |
| day be a spectacular MUD...     | Plan: To make Bill Gates suffer |
---------------------------------------------------------------------