I know vaguely that flatpak is "like docker" in terms of wrapping dependencies.
I have no clue how that translates to missing features of compatibility issues with other apps.
Even knowing which is more up to date isn't shown. Or why i should pick one over the other.
The multiple packaging types confounded my efforts to debug an issue I had with VLC, as i initially thought it was a flatpak permissions problem.. No evidence, just hearsay by what i'd seen of flatpak in general online.
And if the packaging difference does matter (as it did for my vlc issue, one solution only worked for the deb), then an explanation for newbies should be given as to the general expectations for each package type.
Or should I just "git gud" and go digging through ppa/flathub? mailing lists to find a 2013 reply to a post?
> or should I just "git gud"
The opposite. Just blindly click on one. If it works you are done, if not click on a different one.
You are really, really overcomplicating this for no reason.
Same with selinux: Lots of "advice" was just to turn it off completely.
> You would have no idea why
Yes, file a bug to get it fixed instead of leaving other users standing in the rain.
Like for example I've been playing with Kodi and as a deb package you can't install some (but not all) add-ons through the built in UI, you have to go find special apt packages for them and install those outside the Kodi UI. Nowhere is this documented or visible to users--Kodi's webpage doesn't concern itself with how Debian packages it so no mention there, and Debian itself is a black hole of information for end users. The exact same issue is present with RetroArch and its Debian packages version. My bottom line is I always pick a deb package as the very last option and expect pain or confusion when doing so.