Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://docs.flatpak.org/en/latest/first-build.html
You can always just create some scripts and put them in a public repo but the other two options would be more "official".
Right now this is because I don't want to keep running a script out of the user directory all the time to reinstall things, but eventually i want to share packages of some sort. (When I looked I didn't really find a good clean ssh/VNC install/setup package.)
I haven't yet found it in the docs but is it possible to get flatpak to do stuff like replace the sshd.conf, systemctl enable sshd.service, etc and otherwise check/fix configuration stuff at boot?
I don't think there is anything you can do that will allow you to change the Valve owned pieces (today) that won't get overwritten on updates.
You are better off looking at Reddit or the Gaming on Linux forum.