Some quick spot checks (ie picking a few random spots to look at in the manifest) , make it abundantly clear that the issue is the MD5 chunk data, which is causing the huge manifests.

I'm not sure what to do about that, it's not possible to spit it out to a downloading directory at update time because you don't know where that'll be, but there's definitely people that want it.

Maybe emitting it directly into a MD5 folder in the route dir, is the best way to handle it ? Gogrepoc itself never reads this data (and has no reason to , there's no actual point in doing offline MD5 chunk comparison when you'd need to be online to do the repairs anyway), so it'd just be a matter of writing it and deleting any outdated ones when updates are done.

Also making it optional I suppose.

Umm.. if it's temporary data, shouldn't the files be saved in a temporary folder and not in the actual installers archive?
Or maybe make it a subfolder of "!downloading"?

They aren't really "temporary" files more like information that some people want.

GOGRepoC does *use* this information but it always fetches a fresh copy whenever needed (because the primary use cases is either allowing download resumes or repairing a file that failed it's MD5 check but in either case it's pointless attempting to do with data that's out of sync with what's on the GOG servers) so there's no need to save it for functionality purposes.

They can't go in !downloading because !downloading is a subfolder of the install directory which you don't know during an update command. I also don't really think they belong there, since these are more info provided for someone who wants it (like the !info.txt) whereas !downloading is more for stuff that gogrepo is doing.

Okay, I've stopped it saving the MD5 chunk data for now, while I think about how to handle this better.

And here's an in progress version for testing for those who want to.

It won't work on anything except Python 3.11 or greater, which is why I'm not uploading it to the github dev branch.

Please do not try using it with Python < 3.11 (or Python 2.7) because it does absolutely no checking at the moment because I intend to move to dateutils for python <3.11 before I release this for realsies, so what it will do in that scenario is unknown to me but probably involves turning your manifest into hot garbage.

Also make sure any resumes in progress are finished before you use this, it'll delete old resume manifests for incompatibility when it encounters them. I'll implement a nicer thing that just asks if you want to abort and use an older version to finish the in process resumes or trash it when it detects this scenario.

That said:
https://www.dropbox.com/scl/fi/3vjpklrehs89994399epu/gogrepoc.py?rlkey=mtixrng5up32gim9izo18hlbt&amp;dl=0