The resource bundle and resource md5 sums.

[Boudewijn Rempt]

On Tue, 23 Dec 2014, Wolthera wrote:

> So, right now, the resource bundle uses md5 sums to figure out which preset is part of it. However,
> these md5sums, which are stored in the manifest.xml are bogus.

Hm... But they are the only way to figure out whether two resources are 
the same. If the md5sums don't work, we've got a bigger problem!

Right now, the actual details have gone quite fuzzy in my mind, and I'm 
trying to focus on fixing the shortcuts/menu mess, so it's kind of hard to 
figure out what's up.

> I do not know why they are bogus, but I am hoping to implement a bit of functionality that is half
> work-around and half kinda necessary anyway:
> 
> First, Krita always installs all bundles upon start-up.

That's actually something that needs fixing then -- because one of the 
nice things of the bundles is that blacklisted/uninstalled bundles 
shouldn't take memory or startup time.

  > I suggest we us this chance for the bundle
> to collect all the md5sums of the resources it installs.
> 
> Then, we get it to check it against all the manifest md5sums, when these are mismatched, we tell the
> user "Ah, it seems that these brushes have mismatching md5sums with the bundle's manifest. They may
> have gotten corrupted udring download:
> <list of brushes>"
> 
> That way, the user actually can see the use of these weird numbery things.
> 
> Then, when Krita deinstalls a bundle, it'll use the md5sums of what it knows it installed instead of
> the list in the manifest.

We can do that, yes.

> 
> Does this sound like a plan? We can then later figure out why the manifest md5sums are nonsense.
> 
> --
> Wolthera
> 
>