Skip to content

Make ~/.steam available in container

Simon McVittie requested to merge wip/low-hanging-fruit into master

/cc @denittis

Now that we have progress on input hotplugging and Vulkan layers, here are assorted smaller fixes, mostly from Github issues.

I think we also need better test coverage for various situations that can happen. We should probably do tests that involve a mock $HOME with various permutations of things you can do with ~/.steam, for example. Perhaps that doesn't need to be a blocker for this, though.

Things previously in this branch have moved to !177 (merged), !178 (merged), !179 (merged).

  • tests: Log what we're copying

    It isn't always obvious which copy of capsule-capture-libs we're going to use to run the tests.

  • pressure-vessel: Make sure ~/.steam is available in the container

    Previously, we made ~/.steam available in the container as part of $HOME, but if it was a symlink outside $HOME or contained symlinks outside $HOME, their targets were not made available in the container.

    When using the experimental feature of a per-game home directory, we correctly made the targets of symlinks inside ~/.steam available, but not the target of ~/.steam itself (if it was a symlink).

    Fixes: https://github.com/ValveSoftware/steam-runtime/issues/291

Edited by Simon McVittie

Merge request reports