net.lutris.Lutris VS flatpak-external-data-checker

Are you using flatpak? Could be this issue or similar. There are quite a few pitfalls with Wine video decoding unfortunately.

Flatkill is full of misinformation or no longer true information. There're many posts debunking most of their points [1]. Some parts were true a few years ago but aren"t anymore.

For example if VSCode wouldn't have direct access to the file system, it would be unuseable since it doesn't support portals to ask the user to grant it access to specific folders (by selecting them through the file picker).

In the process of packaging an app for flathub, the packager has to provide some reason for why for example full file system access is necessary. The discussion to add or remove permissions are always open [2].

[1] https://theevilskeleton.gitlab.io/2021/02/11/response-to-fla...

[2] https://github.com/flathub/net.lutris.Lutris/issues/229

https://flathub.org/apps/details/net.lutris.Lutris is always best option for lutris, if your distro is okay with flatpak.

Probably easiest to get Lutris as a Flatpak https://flathub.org/apps/details/net.lutris.Lutris

You can install lutris via flatpak. link

Likely related to issues described in https://github.com/flathub/net.lutris.Lutris/issues/85

> Maybe. The CI rules should be made public in that case, though, surely? Maybe they are?

Agreed, but thankfully they are. The PRs link to <https://github.com/flathub/flatpak-external-data-checker>. That said, it'd be clearer if the flathubbot 'user' profile also linked to that URL.

> The enormous amount of value the distros bring [...] is audit of packages (and packaging).

Yes, auditing against supply chain attacks is good! But there's also a risk in running outdated software. I don't have easy answers. But if automation leaves more time for the hard part, great.

Flathub provides an excellent tool to keep your dependencies up to date, so it's just a matter of adding it to the manifests. Besides, who says 'dependencies not being updated enough' is a valid metric to determine the quality of a package? LOL.

According to Github issue/PR #126 new builds are failing because of a bug in flatpak-external-data-checker or some incompatibility between the two projects at least.

I'm surprised the documentation says that since Flathub itself runs its CLI scripts via Flatpak: https://github.com/flathub/flatpak-external-data-checker

Another thing you could add would be to tag your releases on GitHub, add a tag field next to the commit one, and add an x-checker-data section to the manifest so the Flathub bot will automatically open PRs to update the Flatpak release when you update your repository.

See f-e-d-c, and if you're not planing to submit to Flathub, then look at the GitHub workflow example there. Be aware that auto-merging is not acceptable for anything other than extra-data sources.

Unfortunately the maintainership of the Zoom Flatpak on Flathub has been a bit slow, but you can still install it since the Flathub bot do automatic builds whenever there's an update, thanks to the provided flatpak-external-data-checker service.

There is https://github.com/flathub/flatpak-external-data-checker which automatizes the update pull requests including dependencies. Flatpak has other downsides, but security or not getting the latest and greatest is not one of them.