Mail Archives: djgpp-workers/1996/10/10/07:03:57
On Thu, 10 Oct 1996, John M. Aldrich wrote:
>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
Error codes would be a first signal for install to know that there's someting
wrong.
>interpret what djverify reports. Hmm... it's an interesting question.
You'd have to format errors output to the log file in a two-fold manner. Those
usefeul only for the user would begin, say with two asterisks and those
helpful for instal with three. Perhaps DJVERIFY should have a special
command-line parameter that, when used, would make it produce a BINARY report
file to be used ONLY by install. This file would contain detailed information
on all encountered errors.
>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. :)
I'll be glad to cooperate with you!
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
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 -_-_-_-_-_-_-_-_-_
- Raw text -