ok may be I didnt explain it well. Let me try again.
I create an installer with the url defined in the installer script, say http://qa.server.com.
QA team tests the installer and wants to deploy to production. Instead of creating the installer again with the production url "http://prod.server.com", we want to release the installer tested in qa (thats what we should do, right)
Thats why I want to externalize the config settings out of the installer, so we can deploy in various stages (qa, staging, production) etc.,
I am not sure I understand config.cfg, if you could send me any documentation, I would appreciate it.
thanks a lot