Chrome/Chromium Experimenting With Flatpak Packaging
An exciting development for this Linux app sandboxing and distribution tech. This would also help improve Google Chrome/Chromium support outside the likes of RPM and Debian based distributions with a cleaner packaging experience.
That's what he said.
https://www.phoronix.com/news/Chrome-Chromium-FlatpakOpen linkView original on lemmy.ml
7 replies
I’ve been using the Flatpak version of Ungoogled Chromium for a while now (for websites that don’t work natively with Librewolf). Is this really that new?
I'd be more impressed if they stopped bundling random crap. It's their unwillingness to use upstream's dependencies and toolchains that makes Chromium a nightmare to package on Gentoo, and flatpaks are not going to fix that. They bundle clang, rust, and so many additional libraries that the "must keep bundled version to prevent breakage" list is almost 300 items long. This is not the correct way to ensure reproducibility, guys.
chromium seems to serve as a basis for google dominance in the browser space so it makes sense that they would intentionally fuck with it in a way that doesn't let others have full control.
I thought that Flatpak breaks unprivileged user namespaces
Flatpak does block userns. Apps on Android don't get unprivileged user namespaces, and Chromium is at its strongest on Android. So I have to assume there is some way of making it secure inside an app sandbox.
I thought Chrome (and Vanadium on GrapheneOS) are usually preinstalled as system apps, does it have the same limitation?
Thankfully Librewolf still uses AppImage as an option.
The only Flatpak I bother with is the Kodi one because my distro has incompatible (read stable) library version on several things for compiling it and I'm considering just jumping to jellyfin for that, as well.