Doesn’t Steam run basically everything, including the client itself, inside the Steam Container Runtime now?
What makes you think that? I don’t remember any announcements to that effect.
Last time I checked, Steam used pressure-vessel (the container) only for games, not for itself. But I haven’t been following changes in that area lately.
Through some script sleuthing, I did discover that Steam ships several of its own 32-bit and 64-bit libraries, and that paths to both are added to LD_LIBRARY_PATH (search path for library files) when the client is launched by the Steam Runtime, but many files (specifically the Steam Runtime) are only present as 32-bit binaries in ~/.local/share/Steam/ubuntu12_32.
Whether the Steam client uses those is a question someone else less sleep-deprived can answer.
What makes you think that? I don’t remember any announcements to that effect.
Last time I checked, Steam used pressure-vessel (the container) only for games, not for itself. But I haven’t been following changes in that area lately.
Through some script sleuthing, I did discover that Steam ships several of its own 32-bit and 64-bit libraries, and that paths to both are added to
LD_LIBRARY_PATH
(search path for library files) when the client is launched by the Steam Runtime, but many files (specifically the Steam Runtime) are only present as 32-bit binaries in~/.local/share/Steam/ubuntu12_32
.Whether the Steam client uses those is a question someone else less sleep-deprived can answer.