Global plugin installation dir #945
Comments
|
I agree that this is a good idea. Even though OMEMO is planned to be implemented in profanity directly, this feature makes sense. Looking for plugins in |
|
According to https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html the proposal of @flocke to seperate c and python plugins should be used. |
|
Good point! I didn't know about it. |
|
@philipflohr do you want to implement this? |
|
@philipflohr ping :) |
|
@mwuttke97 maybe something for you? |
jubalh
added a commit
that referenced
this issue
Sep 29, 2021
Two options to install plugins. Mention the whole path: `/plugins install ~/src/profanity-plugins/my.py` Mention only the plugin name: `/plugins install my.py` The latter will look in `/usr/local/share/profanity/plugins/` for the file and copy it over to `~/.local/share/profanity/plugins`. At first I was thinking about loading the plugins from the global location. But users most likely don't want to have all plugins activated that an admin installs on a system. Regards #945
jubalh
added a commit
that referenced
this issue
Sep 29, 2021
Packagers can package https://github.com/profanity-im/profanity-plugins or another collection of plugins to `/usr/local/share/profanity/plugins` (python) and `/usr/local/lib64/profanity` (c). `/plugins` will list these globally available plugins now along with the ones thare are installed (`~/.local/share/profanity/plugins`) and loaded. Regards #945
jubalh
added a commit
that referenced
this issue
Sep 29, 2021
Two options to install plugins. Mention the whole path: `/plugins install ~/src/profanity-plugins/my.py` Mention only the plugin name: `/plugins install my.py` The latter will look in `/usr/local/share/profanity/plugins/` for the file and copy it over to `~/.local/share/profanity/plugins`. At first I was thinking about loading the plugins from the global location. But users most likely don't want to have all plugins activated that an admin installs on a system. Regards #945
jubalh
added a commit
that referenced
this issue
Sep 29, 2021
Packagers can package https://github.com/profanity-im/profanity-plugins or another collection of plugins to `/usr/local/share/profanity/plugins` (python) and `/usr/local/lib64/profanity` (c). `/plugins` will list these globally available plugins now along with the ones thare are installed (`~/.local/share/profanity/plugins`) and loaded. Regards #945
|
#1598 got merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would it be possible to create a global plugin location so it would be easier for packagers to distribute plugins?
For example I could package the OMEMO plugin and have it installed directly in the right place without the user having to copy/link a file manually to
~/.local/share/profanity/plugins/afterwards.I would suggest something like
${DATADIR}/profanity/plugins(e.g./usr/share/profanity/plugins) for python plugins and${LIBDIR}/profanity/plugins(e.g./usr/lib/profanity/pluginsor/usr/x86_64-pc-linux-gnu/lib/profanity/plugins) for C plugins.The text was updated successfully, but these errors were encountered: