diafero wrote:I currently see one problem though: The SDL changes I did don't always add the SDL var at the end but rather where it fits regarding the context (like the Yeesha Pages, they are all in one place). If your script now does it differently, we would have incompatible sets of SDL files.
That's not a problem. The installer looks for the presence of the vars anywhere in the last STATEDESC, deletes them if present, then adds all changes at the end. They are no longer grouped according to context, they are grouped by distribution, which makes more sense anyways. You can add a comment such as "These are changes from distro #1234567"
I'll post an example soon because I finished testing this part of the installer last night.
diafero wrote:The installer should also offer a way to provide the full STATEDESC block of one or more new SDL versions which is then simply attached to the current file. This would make sure the SDL files are the same as in the current Offline KI.
Not sure I understand. Aren't previous versions irrelevant? The last block must have all variables.
Anyway, the patcher lets you do that with the xml file.
diafero wrote:What we'll also have to think about is an update path. The installer has to be able to patch from a clean install to the current Offline KI (or whatever is deployed) as well as from a previous to the current version.
Maybe. My main goal was to be able to add to the user's existing installation without needing a clean install.
diafero wrote:EDIT: Oh, and which language do you write that script in? Will it also be usable on non-Windows systems (which I think it should)?
VBScript
Well I didn't start with an installer project, I just needed a few DOS batch files for automating my work. Batch commands are too limited so I switched to VBScript. Then it kinda mutated into an installer. Then it hit me that I should have done that in Python and learn the language at the same time.
Maybe for the next version.