Skip to content
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

TODO: runtime container customization #4

Open
GloriousEggroll opened this issue Jan 24, 2024 · 0 comments
Open

TODO: runtime container customization #4

GloriousEggroll opened this issue Jan 24, 2024 · 0 comments

Comments

@GloriousEggroll
Copy link
Member

  • use our own runtime container based on valve's instead of using valve's, this way we can add/remove things from the container as needed
R1kaB3rN added a commit to R1kaB3rN/ULWGL-launcher that referenced this issue Apr 20, 2024
- For now, hide this tool in the Steam client until the umu runtime platform is released.

- Related to Open-Wine-Components#4
R1kaB3rN added a commit that referenced this issue Apr 24, 2024
- For now, hide this tool in the Steam client until the umu runtime platform is released.

- Related to #4
R1kaB3rN added a commit that referenced this issue Apr 25, 2024
* umu_consts: update logic

* umu_plugins: delete enable_flatpak function

- For now, execute the launcher within the Flatpak sandbox. Breaking out the sandbox via flatpak-spawn is discouraged and breaks Flatpak's security model. It may also require other Flatpak applications to make additional changes in their manifest, which they may not be supportive to do for this practice. Unless necessary or proven to be very problematic, execute within the Flatpak sandbox

* umu_util: only copy umu_version.json and reaper

- To run games, the only required files to be in the user's home directory is the runtime platform and the reaper executable. The launcher files will remain in their system path that's been configured in build time.

* Update Makefile to install umu-launcher in system path

- The directory /usr/share/steam/compatibilitytool.d is an official system path supported by Valve's Steam client to search for community-based tools and to use them as compatibility tools to run games. Instead of copying the umu-launcher directory to ~/.local/share/Steam/compatibilitytool.d we can install it in its system path. That way, there's less to copy/remove and the files there can be managed by the distribution's package manager

* umu_util: don't pass compatibilitytools.d path

- The system path compatibilitytools.d directory will be used instead

* umu_consts: delete enum

* umu_run: update debug message

* flatpak: limit access to ~/.local/share/Steam

- The launcher only needs this directory to write Proton. For now, just limit access to this directory instead of exposing user's entire ~/.local/share

* umu-launcher: hide umu-launcher compatibility tool

- For now, hide this tool in the Steam client until the umu runtime platform is released.

- Related to #4

* Update tests

* umu_plugins: remove enable_reaper

* umu_run: add reaper to command list

* umu_util: don't copy reaper

- Reaper can be executed directly from the system path. All we need in the home directory is the runtime platform

* umu_util: update launcher and runner

- While those files will not be copied anymore, we still need to update them in umu_version.json if we want the configuration files to be in sync

* Update tests

* umu_test: update tests

- Update the tests to account for the launcher files, umu-launcher and reaper not being copied to the home directory. Those files will remain in their system path defined at buid time, which makes the umu_version.json in ~/.local/share/umu and the runtime platform the only files in ~/.local/share/umu.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant