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

Flatpak Support #10

Open
SeongGino opened this issue Nov 27, 2024 · 0 comments
Open

Flatpak Support #10

SeongGino opened this issue Nov 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@SeongGino
Copy link
Owner

I've never actually looked at or done anything with Flatpak outside of using some (select few) apps through it, so I'm not sure what the requirements of Flatpak support are.

FWIW: regarding filesystems, we rely currently on a couple of things that are found in the local filesystem:

  • umu-run itself, because duh
  • curl for external downloading (currently only used for downloading the Discord Bridge service, but will be used elsewhere), waiting on another issue to pack this in as a build dependency rather than runtime.
  • ~/.steam/steam/compatibilitytools.d for finding existing Steam Proton runners - not completely necessary, as Nero Manager can simply make its own directory that it uses to store runners.
  • ~/.config for the manager configuration file, which stores the prefixes path and basic settings for the frontend.
  • Whatever gets defined as the prefixes "Home"
  • /tmp, for storing either downloads (currently only Discord Bridge) or icons extracted from applications.

Nero Manager also provides a system tray icon, but I assume Flats should be able to use these just fine?

I have to assume, due to sandboxing, that any access to filesystems needs to go through some kind of filter or some shit?

@SeongGino SeongGino added the enhancement New feature or request label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant