Explaining the current Steam Package build: Difference between revisions
m →chroot: made more formal |
m Outdated |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{outdated|Steam's packaging has considerably changed since this article was written.}} | |||
This article should give insight about how steam is currently packaged and how and why it works like this. It also discusses what the problems are in packaging it and how we can approach solving them. | This article should give insight about how steam is currently packaged and how and why it works like this. It also discusses what the problems are in packaging it and how we can approach solving them. | ||
| Line 16: | Line 17: | ||
** this method would allow us to have binaries in the expected paths without disrupting the system. | ** this method would allow us to have binaries in the expected paths without disrupting the system. | ||
** Steam itself, as well as Valve games and perhaps others like to checksum their executables, so patching does not work. | ** Steam itself, as well as Valve games and perhaps others like to checksum their executables, so patching does not work. | ||
* Cons: Performance might suffer from this, but we are not sure. | * Cons: | ||
** Performance might suffer from this, but we are not sure. | |||
** Kernel patch is required for SteamVR asynchronous reprojection.<ref>https://lvra.gitlab.io/docs/distros/nixos/#steamvr</ref><ref>https://github.com/NixOS/nixpkgs/issues/217119</ref> | |||
=== Link bash to /bin and glibc/lib to /lib and be happy === | === Link bash to /bin and glibc/lib to /lib and be happy === | ||