-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please consider making --command=steam go via the wrapper #1078
Comments
@smcv this sounds fine, I actually considered it years back but wasn't sure if it was considered supported approach from Steam side. |
nanonyme
added a commit
that referenced
this issue
Aug 13, 2023
As suggested by smcv in #1078 let's make /bin/steam be wrapper script. This decreases probability of users accidentally bypassing wrapper and getting unexpected end results and facilicates some future use cases.
nanonyme
added a commit
that referenced
this issue
Aug 13, 2023
As suggested by smcv in #1078 let's make /bin/steam be wrapper script. This decreases probability of users accidentally bypassing wrapper and getting unexpected end results and facilicates some future use cases.
nanonyme
added a commit
that referenced
this issue
Aug 13, 2023
As suggested by smcv in #1078 let's make /bin/steam be wrapper script. This decreases probability of users accidentally bypassing wrapper and getting unexpected end results and facilicates some future use cases.
nanonyme
added a commit
that referenced
this issue
Aug 27, 2023
As suggested by smcv in #1078 let's make /bin/steam be wrapper script. This decreases probability of users accidentally bypassing wrapper and getting unexpected end results and facilicates some future use cases.
nanonyme
added a commit
that referenced
this issue
Aug 27, 2023
As suggested by smcv in #1078 let's make /bin/steam be wrapper script. This decreases probability of users accidentally bypassing wrapper and getting unexpected end results and facilicates some future use cases.
This is now changed in beta. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment
/app/bin/steam
is Valve'sbin_steam.sh
(which users should never run directly in this Flatpak app), and/app/bin/steam-wrapper
is the correct entry point for users (which does some necessary setup and then execs/app/bin/steam
).With flatpak/flatpak#5404 and flatpak/flatpak#5395 in mind, it might be better to have
/app/bin/steam
be the wrapper, and make it exec Valve's script as/app/lib/steam/bin_steam.sh
(or via a symlink/app/lib/steam/steam
after prepending/app/lib/steam
to thePATH
, if having it available in thePATH
assteam
is desirable).That would make it less likely that users will get broken behaviour by running it with
--command=steam
. If flatpak/flatpak#5404 gets merged, it would also allow thesteam
executable to be exported as a more explicit entry point/var/lib/flatpak/com.valvesoftware.Steam+steam
alongside/var/lib/flatpak/com.valvesoftware.Steam+steamcmd
./app/bin/steamcmd
is already a symlink tosteamcmd-wrapper
, ensuring that--command=steamcmd
goes via the wrapper as expected, instead of running Valve's code directly.The text was updated successfully, but these errors were encountered: