You may be interested in reading this post about the process of packaging Steam.

tl;dr: It’s mostly an annoyance reserved for packagers to deal with. Dynamically linked executables can be patched in a fairly universal fashion to work without FHS, so that’s the go-to approach. If the executable is statically linked, the package may have to ship a source patch instead. If the executable is statically linked & close-source, the packagers are forced to resort to simulating an FHS environment via chroot.

Nah, dump em’ to /tmp/ and let the user figure out the rest

The story is more interesting than the title suggests! This guy was arrested for hacking two telecom companies, got released under investigation, then immediately hacked Nvidia before being put under house arrest. After that, he was relocated to a hotel (due to being doxxed) where all he had to work with was a Fire TV stick, which he promptly then used to hack Rockstar.

All in all, he’s believed to have stolen $14 million+. By the way… he’s 18, autistic, and enrolled in a special education school.

I’m a plaintext git patch sent via email and lost in the maintainer’s spam folder