krusynth
commented
7 years ago We need a bunch of metadata here as well as the md5 hash of each mod, so we'll probably want to create a lock file that's updated on installation of mods. This should store the hash, the version number, and the source url for the mod file; effectively a database of info about the installed mods.
I've considered a couple of schemes and this seems the most doable. My "runner-up" would be to create a separate mod folder for installation, where each mod is housed in its own folder, and then that an info file in each folder; the "real" mod folder would then only have symlinks to the actual mods. That seems... overly complicated for this.
Ideally, we should be able to deliver the packages to a Technic installer or other mod loader. The API for Technic is pretty simple, so we could just generate static json files for this, instead of forking/modding Solder. Technic also allows specifying the url of mods instead of just providing them directly, so we can pass through to the original sources, we just need to create the md5 hash of each.