Thank you for helping to keep GamingOnLinux civil and safe!
Please tell us why you're reporting this content. Please note we store your IP address for all reports to help prevent spam and abuse. You can also email any complaints to: [email protected].
- Survive an elevator trying to eat you in co-op horror KLETKA when it releases February 19
- Draft code submitted to KDE Plasma turns it into a full VR desktop
- Proton Experimental brings updates for MonoGame, Rockstar Launcher and more
- Valve tweak Steam AI disclosure form for developers to clarify it's for content consumed by players
- No Rest for the Wicked co-op update lands on January 22 and it hit a big sales milestone
- > See more over 30 days here
- Casual/Social places for developer chatter
- simplyseven - Will you buy the new Steam Frame?
- eev - One-time logout
- Liam Dawe - Away later this week...
- Liam Dawe - Weekend Players' Club 2026-01-16
- grigi - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
A. Distro independence. By having every package keep to itself differences between distros don't hurt the packages.
B. Unsigned proprietary packages. FOSS packages are easy to verify, because you can inspect them for unwanted behavior. Especially, since uncovering the tools used is one of the primary ways to identify malware developers. It's, why many repositories can include packages from people they wouldn't normally trust or even totally anonymous sources. For proprietary packages you don't have this luxury unless your name is Apple. As such the trust placed in proprietary packages normally flows directly from the trust in their developer, which is achieved with having them sign their packages. Now the question arises, what if we want proprietary packages, but their developer refuses to support our obscure package manager and thus sign it. This is where the hybrid approach of containerization comes in: you might not be able to inspect the code, but you can inspect the container limits and at least assure yourself it doesn't touch anything it shouldn't touch.