Repository navigation
Why do my SHA1 checksums differ from that in the game_db XML/JSON?? #2427
|
What am I doing wrong/what's going on here? For example... From the XML.. From my shell ... sha1sum SpaceQuestEnhanced_v1.3_MT32_2222.lha What am I missing here? TIA |
Replies: 2 comments 2 replies
|
Nothing is wrong on your side. That sha1 is the hash of the whole .lha file the database builder scanned when it added the entry, so any copy that isn't byte for byte identical to it (repacked later upstream, or taken from a different set) gets a different hash even when the game files inside are the same. Amiberry picks the entry if either the filename or the sha1 matches (amiberry_whdbooter.cpp, the XML path does the same a bit further down), so the hash only matters for renamed archives. As long as your file is still called SpaceQuestEnhanced_v1.3_MT32_2222.lha, it gets that entry's settings anyway. |
|
Thanks....but doesn't that make the sha1 hash more or less superfluous for file identification purposes? |
Mostly, yes, as long as the archive keeps its original name. The sha1 is the fallback for renamed files: if you call the .lha something else, the filename lookup misses and the hash still finds the entry, but only when it's the exact file the database was built from.