Erick555

It seems that pipewire developers had [different plans](https://github.com/flatpak/flatpak/pull/1020) for flatpak support instead of using socket.

I think it may be common problem with read-only permissions of perl libs after install. Example fix is [here](https://github.com/flathub/org.gmusicbrowser.gmusicbrowser/blob/bea4573081a37ef90591534a2d4d2efaa263eca7/perl-libs.json#L16).

Which extensions needs different Sdk version than Platform? In such case there is no abi compatibility guarantee which may lead to (un)expected brokenness. Allowing for messing this up is potential...

Ok. The problem I see now is it's backwards incompatible change - all older f-b would fail to properly build new manifest. Maybe it's not worth it if there is...

The point is: why bother? Why break backward compat only to fix pure cosmetic issue? I doubt adjusting manifest for this is worth anyone time.

I could agree yet not every bug is worth fixing.

The problem with relying on simple keys is that many projects handle them quite loosely. It's not uncommon for changing signing key without a notice and without establishing chain of...

Wouldn't there be silent failures in such case? `-f` is to force the patch even if it looks wrong which is opposite of what we need - always fail immediately.

[This](https://stackoverflow.com/questions/37157658/patch-run-in-non-interactive-mode/37158127#37158127) suggests `-f` will exit with non-zero code when patching wrong file. I'm not sure about: > Assume that the user knows exactly what he or she is doing, and...

@mwleeds I just hit the same issue. Did you found any workaround for installing flatpak system-wide?