Mail Archives: djgpp-workers/1999/04/12/13:37:05
On Mon, 12 Apr 1999, Laurynas Biveinis wrote:
> It's a really bad thing to have such autoexec.bat where next path=...
> overwrites
> previous. My installer will not create a new problem, it will reveal an old
> one.
Just because PATH is set to something else doesn't necessarily mean that
constitutes a 'problem'. Not by a wide margin. Just to given an example:
I have multiple configurations, but only *two* PATH settings:
PATH=one path list
if %config%==blabla PATH=another path list
> OK, now about multiconfiguration...
> 1) If user knows how to setup multiconfigurations, he will be able to
> install DJGPP by himself.
Correct. Actually, I think you should be *extremely* careful editing
autoexec in any kind of automatic way. There's good reason almost
no commercial installer tries to do that.
My recommendation would be: copy autoexec.bat, change the *copy*, and
ask the user to manually
a) check the changes thoroughly
b) move to the new version if all's well, backing up the previous one.
Or at least show all changes to be made, *before* actually changing
autoexec.bat, and only if the user says they're OK, do them. If he says,
no write an edited copy so he has something to start off from when doing
the changes manually.
> 3) For multi-confs my idea is:
> * Read from config.sys all configuration names and their descriptions
It's probably wisest to just give up immediately when multiple
configurations are detected.
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -