Skip to content
Snippets Groups Projects
  1. Jan 05, 2021
  2. Dec 08, 2020
  3. Nov 19, 2020
  4. Nov 18, 2020
    • Simon McVittie's avatar
      system-info: Detect whether the expected runtime linker is present · 559bdc0a
      Simon McVittie authored
      
      On operating systems with unusual path layouts, such as Exherbo and
      NixOS, the de facto standard path for the runtime linker is not
      necessarily present for all architectures.
      
      (Of course, if the x86_64 runtime linker is not present, we won't
      normally be able to run steam-runtime-system-info either, but at least
      users of such operating systems can compile it from source code if they
      need to provide diagnostics.)
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      559bdc0a
  5. Nov 17, 2020
  6. Oct 26, 2020
  7. Oct 07, 2020
  8. Sep 29, 2020
  9. Sep 25, 2020
  10. Sep 22, 2020
  11. Sep 21, 2020
  12. Sep 07, 2020
  13. Jul 29, 2020
  14. Jul 09, 2020
  15. Jun 10, 2020
  16. Apr 24, 2020
  17. Apr 06, 2020
  18. Apr 03, 2020
  19. Apr 02, 2020
  20. Apr 01, 2020
  21. Mar 06, 2020
  22. Mar 05, 2020
  23. Feb 10, 2020
  24. Nov 08, 2019
  25. Oct 31, 2019
  26. Oct 11, 2019
  27. Sep 26, 2019
  28. Sep 25, 2019
    • Simon McVittie's avatar
      Distinguish between the Steam installation (root) and data paths · 41ac7a82
      Simon McVittie authored
      
      Until now we've been conflating these two, but Timothee Besset recently
      clarified their status for me.
      
      ~/.steam/steam is maintained by bin_steam.sh, aka /usr/bin/steam,
      in which it is referred to as STEAMDATALINK. It is the data directory
      containing user data (cloud-synced configuration and saves), the
      download cache, and the default Steam Library directory.
      
      ~/.steam/root is maintained by steam.sh, in which it is referred to as
      STEAMROOTLINK. It is the installation directory, containing Steam
      executables and libraries.
      
      As a result, they are normally the same, but can differ, in particular
      in two situations:
      
      * When testing a new Steam client build by running client/steam.sh,
        client/ gets used as the installation directory, in conjunction with
        the existing data directory pointed to by ~/.steam/steam. This avoids
        having to re-login or re-download your library of games for the new
        test installation.
      
      * When Debian bug #916303 was present during the initial Steam
        installation, the Steam client was unpacked into ~/.steam, resulting
        in creation of ~/.steam/steam as a real directory that cannot be
        replaced with a symbolic link. We effectively ended up using
        ~/.steam as the installation path, but with ~/.steam/steam as the
        data path. (The Debian steam package has since been fixed, but we
        cannot easily disentangle existing installations.)
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      41ac7a82
  29. Aug 15, 2019
  30. Aug 13, 2019
  31. Aug 12, 2019
  32. Aug 02, 2019
  33. Jul 29, 2019
Loading