Skip to content
Snippets Groups Projects
Commit 82bbfa13 authored by Simon McVittie's avatar Simon McVittie
Browse files

docs: Update status of sniper in slr-for-game-developers


sniper is now available to the public, and there is one game using this
runtime in its development branch already.

Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
parent a6abc5c0
No related branches found
No related tags found
1 merge request!470Update slr-for-game-developers, compat-tool-interface documents
......@@ -98,24 +98,29 @@ scout.
Steam Runtime version 2, codenamed soldier, is based on Debian 10 (2019)
and is already available to the public.
As of 2021, it is not possible to ship games on Steam that will require
soldier or newer container runtimes.
We hope this will become possible in future.
However, if it is useful to run in a newer container during development,
the *Steam Linux Runtime - soldier* compatibility tool can be used to
achieve this.
Steam Runtime version 3, codenamed sniper, is not yet available to the
public (although private builds already exist).
It is expected to be very similar to soldier, but based on Debian 11 (2021)
instead of Debian 10 (2019), with correspondingly newer versions of various
shared libraries and other packages.
Steam Runtime version 3, codenamed sniper, is very similar to soldier.
It is based on Debian 11 (2021) instead of Debian 10 (2019), with
correspondingly newer versions of various shared libraries and other
packages.
For commands, filenames, etc. in this document that refer to `soldier`,
substituting `sniper` will usually provide a similar result for the sniper
runtime.
As of mid 2022, releasing games on Steam that require the soldier, sniper
or newer container runtimes is not possible without manual action by the
Steam developers.
A development branch of Battle for Wesnoth is the first example of
[a game using the sniper container runtime][wesnoth-sniper].
We hope this will become available for general use in future.
[wesnoth-sniper]: https://github.com/ValveSoftware/steam-runtime/issues/508#issuecomment-1147665747
If it is useful to run in a newer container during development,
the *Steam Linux Runtime - soldier* or
*Steam Linux Runtime - sniper* compatibility tools can be used to
achieve this.
### Windows games, using Proton
Versions 5.13+ of Proton require recent Linux shared library stacks.
......@@ -174,6 +179,7 @@ For a more scriptable version of this, launch one of these URLs:
* Steam Linux Runtime (scout): `steam steam://install/1070560`
* Steam Linux Runtime - soldier: `steam steam://install/1391110`
* Steam Linux Runtime - sniper: `steam steam://install/1628350`
* Proton Experimental: `steam steam://install/1493710`
* Proton 6.3: `steam steam://install/1580130`
* Proton 5.13: `steam steam://install/1420170`
......@@ -181,7 +187,7 @@ For a more scriptable version of this, launch one of these URLs:
### Running commands in soldier, sniper, etc.
The simplest scenario for using the Steam Linux Runtime framework is to
run commands in a newer runtime such as soldier (or, in future, sniper).
run commands in a newer runtime such as soldier or sniper.
This is not directly supported by Steam itself, but is useful as a
baseline for testing.
To do this, run a command like:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment