From 2c3194e1f32c9e42a78641649a91c28db2c9ff22 Mon Sep 17 00:00:00 2001
From: Simon McVittie <smcv@collabora.com>
Date: Wed, 20 Nov 2024 19:02:17 +0000
Subject: [PATCH] launch-client(1): Put a simple SLR 3.0 example first

Now that SLR 3.0 is widely available, it makes sense to use it as our
first example: it's the simplest, and both SLR 1.0 and Proton build
on the foundation that the SLR 2.0 and 3.0 container runtimes provide.

Signed-off-by: Simon McVittie <smcv@collabora.com>
---
 bin/launch-client.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/bin/launch-client.md b/bin/launch-client.md
index 6c25a1962..0882d357d 100644
--- a/bin/launch-client.md
+++ b/bin/launch-client.md
@@ -448,6 +448,29 @@ A copy of **steam-runtime-launch-client** can be found in
 or
 `.../steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/`.
 
+For a Steam game that runs under the "Steam Linux Runtime 3.0 (sniper)"
+(or newer) compatibility tool,
+such as Team Fortress 2 (app ID 440),
+if you set its Steam Launch Options to
+
+    STEAM_COMPAT_LAUNCHER_SERVICE=container-runtime %command%
+
+you can run debugging commands inside the container,
+in this example **wflinfo**(1):
+
+    $ steam-runtime-launch-client --list
+    --bus-name=com.steampowered.App440
+    --bus-name=com.steampowered.App440.Instance54321
+
+    $ steam-runtime-launch-client \
+        --bus-name=com.steampowered.App440 \
+        -- \
+        wflinfo --platform=glx --api=gl
+
+`wflinfo` and its arguments can be replaced by any command and arguments
+that will run successfully inside the container,
+for example `steam-runtime-system-info`, `xterm` or `bash -i`.
+
 For a Steam game that runs under Proton 7.0 or later, if you set its
 Steam Launch Options to
 
-- 
GitLab