Matthias Klumpp

Using appstream-glib for this is no longer ideal, because it does not validate a lot of new concepts used in AppStream today. Validating with `appstreamcli` instead gives you: ``` ~$...

> Is appstream-util still maintained or completely abandoned? I think @hughsie would call it "deep maintenance mode" ;-) - no major new features, but bugfixes are still applied and releases...

I don't think it makes much sense to change release processes for a project that is in deep maintenance mode and will likely only get few bugfix releases. For your...

That depends on whether there will be a new full-time maintainer who can take on the work - see https://github.com/gnunn1/tilix/issues/1700

The Flatpak stuff really needs an update - patches welcome! ;-)

AppStream is backwards-compatible, but has never been (and will not be) forward-compatible. Here, the version of appstreamcli is simply too old to validate metadata that was written for a newer...

From my experience, allowing a "just ignore warnings/validation" flag is a recipe for disaster, unless it can be limited to builds or actions that are guaranteed to never leave the...

> This is before we even get to the issue of offline building, or whether go-appimage should silently be making network requests in a way that cannot be disabled. Passing...

> Since which version is `--no-net` supported? Pretty much forever, since `validate` existed. There's no version without it.

> @s-ludwig is still a bit wary about complicating dub with the logic of figuring out where to install system binaries as this heavily depends on the distro. It's not...