Update documentation around launch-client(1)
Documentation issues that I noticed while looking at steamrt/tasks#145.
The only functional change here is to emit a couple of warnings:
DEBUG:test-launcher:Starting launcher with socket
steam-runtime-launcher-service[606538]: W: The --socket option is deprecated. Prefer to use --session or --bus-name.
…
DEBUG:test-launcher:Starting launcher with socket directory
steam-runtime-launcher-service[606690]: W: The --socket-directory option is deprecated. Prefer to use --session or --bus-name.
-
launch-client(1): Update status of Flatpak branches
Flatpak 1.12 supports the --app-path and --usr-path options, and was released a while ago.
-
launcher-service(1): Add --[no-]stop-on-exit to synopsis
-
launcher-service(1): Remove details of how it was used in the past
Since the removal of PRESSURE_VESSEL_RELAUNCH_CONTAINER=0, we no longer use launcher-service for routine game launching, only for debugging.
-
launcher-service: Document private sockets as deprecated
Now that we're only using this tool for debugging and not for routine game-launching, we don't need to accommodate systems where the well-known D-Bus session bus is missing or broken.
-
launch-client(1): Clarify documentation of --clear-env
-
launch-client(1): Document --directory correctly
The documentation implied that --directory="" was the default, but actually it isn't. Perhaps it should be, but for now, make the man page document the reality.
-
launch-client(1): Update --forward-fd to mention pseudo-terminals
-
launch-client(1): Provide some more-real-world examples