Steve Kemp wrote: > [...] > I think that aborting if the file doesn't exist is too strong > a reaction..
There is technically no use to give a non-existing config file - that is clear because it's just ignored, if it doesn't exist - no action is taken. So, if a user gives --config with an unexisting file it is therefore very likely a typo, which the user wants to be warned as fast as possible. In this case, there's no use to run the install until the end with an unwanted configuration - the user wants to run again, with the right config file. If not error is given, and not stopped, it takes a long while to find out that the wrong configuration is installed. Henning -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
