776
Feature requests / Re: integrated mod installer
« on: 18 November 2010, 16:42:34 »
yeah I was expecting to author the zip or 7z archive directly to turn a range request into a full archive.
my python script was not intended in any way to be the codebase that gets adopted, but rather I simply wanted to know what fraction of a mod altered for each iteration and how big the diffs might be; not find a quick way to determine that, I wrote that throw-away python script.
I feel uncomfortable with a tar+xdelta approach and would prefer an approach where the xml of a mod was parsed in the same way the game does, all dependencies located, and all the appropriate bits getting zipped up along with meta information. It might be that the end result is an archive, but the way to get there is quite different and more involved.
The appeal of HTTP range requests is the simplicity of hosting.
So rather than a script that just thinks about directories, a tool that actually parses and packages the mod. That's my general outlook.
my python script was not intended in any way to be the codebase that gets adopted, but rather I simply wanted to know what fraction of a mod altered for each iteration and how big the diffs might be; not find a quick way to determine that, I wrote that throw-away python script.
I feel uncomfortable with a tar+xdelta approach and would prefer an approach where the xml of a mod was parsed in the same way the game does, all dependencies located, and all the appropriate bits getting zipped up along with meta information. It might be that the end result is an archive, but the way to get there is quite different and more involved.
The appeal of HTTP range requests is the simplicity of hosting.
So rather than a script that just thinks about directories, a tool that actually parses and packages the mod. That's my general outlook.
