Matthias Klumpp

> I was thinking about preserving compatibility with appstream-glib because you can be using flatpak with this patch, but flatpak-builder with composing done by appstream-glib. Yes - but doesn't appstream-glib...

As expected, GDC didn't like the change (it's version (4.8) is *really* old on Travis, 8.1 would work though). I excluded GDC from running Meson on the CI, so everything...

Is there any work going on on this? I am using enumerations quite a lot, and no support in Hibernated makes the software a lot less useful.

This is tricky, because more formats mean more complexity and we can only have one - so all frontends need to support the format first. I actually played around with...

> @ximion is writing a new `appstream-compose` library to replace the `appstream-builder` library. That thing is pretty much complete, `appstream-generator` uses it already. While its API isn't marked as "stable"...

I've always considered the `appstream-data` package method of delivering the data as a workaround. The ideal way to ship this data is as part of the regular repository metadata, as...

That's the annoying thing with tar files: They don't have an index. So far this hasn't been much of an issue, as there are only few large packages, but since...

Skipping over large data chunks is *waaaaaay* faster than extracting anything and dealing with disk write *and* read I/O. Also, what would "too often" even be ;-) Creating a hash...

I'd say yes, because the data structure needed would hold very specific information about the individual archive. But I'll have to look again how the decompressor is used (haven't looked...

Usually this isn't an issue as data doesn't move *that* fast - for example, Debian runs the cleanup step once a week which is perfectly fine. If you update hourly,...