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 #44

Open
eruizc-dev opened this issue Dec 12, 2023 · 0 comments
Open

Flatpak support #44

eruizc-dev opened this issue Dec 12, 2023 · 0 comments

Comments

@eruizc-dev
Copy link

eruizc-dev commented Dec 12, 2023

Flatpak is a package manager that installs applications in a sandbox, which is great for developers as they can package their applications with their dependencies without having them missing or conflicting with the dependencies of other applications but for extensions it may be painful as there is no way for users to install d2 package inside the sandbox. Even tho it is possible to share directories with the sandbox, common binary locations like /bin or /usr/bin are blacklisted and cannot be shared from the host to the sandbox.

The solution would be to use flatpak-spawn and run flatpak spawn --host /usr/bin/d2 within the sandbox instead of plain d2, it would be nice if this plugin allowed in the settings to provide a custom executable instead of just the path. Looking at the code I didn't found any way to do that currently, but it could be achieved.

Workaround

In the meantime I copied the d2 executable into the sandbox with this command, however it will get removed the next time Obsidian gets updated.

sudo move /usr/bin/d2 /var/lib/flatpak/app/md.obsidian.Obsidian/current/active/files/bin
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