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

Describe alternative to packaged extensions to add 'plugins' to application #178

Closed
gbraad opened this issue May 3, 2019 · 0 comments · Fixed by #419
Closed

Describe alternative to packaged extensions to add 'plugins' to application #178

gbraad opened this issue May 3, 2019 · 0 comments · Fixed by #419

Comments

@gbraad
Copy link

gbraad commented May 3, 2019

As described on the mailinglist by @alexlarsson :


So, each installation (e.g. /var/lib/flatpak, and
~/.local/share/flatpak as well as other customly added ones) can have
a subdirectory called "extension".

In this directory you can create
directories named $ref/$arch/$branch, and the contents of that will be
directly visible as the content of the plugins (i.e. what would be in
the "files" subdirectory of the deploy dir if you installed a packaged
version of the plugins).

So, for example, if you create a directory called:
~/.local/share/flatpak/extension/io.github.Hexchat.Plugin.Gerard/x86_64/18.08
Its contents would appear under /app/extensions/Gerard in the hexchat sandbox.

Note, the details above matches this from the hexchat manifest:

  "add-extensions": {
    "io.github.Hexchat.Plugin": {
      "version": "18.08",
      "subdirectories": true,
      "directory": "extensions",
      ...
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

Successfully merging a pull request may close this issue.

1 participant