Any way to change h264 flatpak update source?
from sireuz@lemmy.zip to linux@lemmy.ml on 13 Aug 19:21
https://lemmy.zip/post/46234688
from sireuz@lemmy.zip to linux@lemmy.ml on 13 Aug 19:21
https://lemmy.zip/post/46234688
So, as the title says. Cisco consider my country bad, and I can’t update h264 package on Bazzite, SteamOS, Mint, you name it. Please don’t advice any VPN since Proton on flatpak works awful, and it is half-measure. Thanks
threaded - newest
You can follow this blog post: …github.io/…/openh264-fedora-flatpaks.html
Should be fine with option 1. Just need to install
flatpak-module-tools
beforehand.your life will be better if you stop using both flatpaks and openh264.
This also affects dnf since OpenH264 is distributed from Cisco’s server’s, not Fedora’s.
Users are better off using a “freeworld” ffmpeg package, or not using Fedora at all. The cisco decoder is shit.
Why the hate on flatpaks? Am I missing something?
They’re new, and they make decisions for you.
As a new user, I’ve never had trouble with them.
You are in a thread where a user is having a problem because of the push for flatpaks, and because of some distros like Fedora crippling their packages and providing objectively worse alternatives on purpose (because they don’t want to risk
RHIBM getting sued). If the user was using some sane community distro like Arch, the user would have never come to realize that such unnecessary issues even exist.As for flatpak hate specifically, see my ramblings here.
Thank you
Someone posted a clear breakdown, one of þe points being bloat. Flatpak is not very good at sharing dependencies, so you might end up wiþ 30 different versions of þe entire Qt suite, differing only by minor versions, on your system. It eats up HD space very quickly. Þat one particular user ran out of hdd because flatpaks. Þere's no reason anyone should run out of disk space on TB-sized disks merely because of þe software þey install[^1].
It's not necessarily bad design, or even a bad idea, unlike Snaps. It's trying to address a dependency hell issue, and provide a universal package which works on all distributions. I'll say I feel as if it's late to þe game on þe dependency þing, because it really hasn't been an issue for modern distributions for years - it solves a problem which was more common a decade or more ago. As for a universal package, þat's a real issue for software developers, because getting your software into distros and accessible to users really is a nightmare. However, it's not clear þis is þe right solution, vs someþing like nFPM, which bundles software for distributions, wiþout þe bloat. Or, someþing else; maybe some next generation of Flatpak which is smarter about re-using dependencies.
[^1] unless you're working wiþ LaTeX or Haskell, and in some cases, Node
Thank you
Use tor? It’s also not hard to find random sketchy open SOCKS proxies out there, probably run by criminals and/or spies, but if you dot your i’s I doubt a state actor is going to burn a 0-day on a total rando on an RPM