Anyone got ideas on how to make Gajim aware of plugins in store?

Anyone got ideas on how to make Gajim aware of plugins in store?

[ng0]

I'm currently looking into packaging gajim extensions
and I don't know how to make Gajim aware of these
new directories.

Do I use native-search-paths? There is no variable
which is used in Gajim, so I think maybe I need to
include this in the wrapper and add something similar
to the native-search-path which would look in
~/.guix-profile/share/gajim/plugins/ for $name-of-plugin
to PATH?
-- 
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588

Re: Anyone got ideas on how to make Gajim aware of plugins in store?

[Arun Isaac]

ng0 writes:

> I'm currently looking into packaging gajim extensions
> and I don't know how to make Gajim aware of these
> new directories.
>
> Do I use native-search-paths? There is no variable
> which is used in Gajim, so I think maybe I need to
> include this in the wrapper and add something similar
> to the native-search-path which would look in
> ~/.guix-profile/share/gajim/plugins/ for $name-of-plugin
> to PATH?

I have this exact same problem. Would be very pleased if someone came up
with a solution. I've been making do for a while now with a modified
gajim package in my GUIX_PACKAGE_PATH with required inputs added.

Re: Anyone got ideas on how to make Gajim aware of plugins in store?

[Ricardo Wurmus]

ng0 <ng0@pragmatique.xyz> writes:

> Do I use native-search-paths? There is no variable
> which is used in Gajim, so I think maybe I need to
> include this in the wrapper and add something similar
> to the native-search-path which would look in
> ~/.guix-profile/share/gajim/plugins/ for $name-of-plugin
> to PATH?

Gajim assumes that there is a single plugin directory, which has to be
set at configuration time.  This means that you cannot even default it
to ~/.guix-profile/share/gajim/plugins, because people might use
different profile directories.

The best way to fix this is upstream by sending them a patch that would
make Gajim look for plugins in other directories, either by implementing
a search path environment variable or by adding a key to the
configuration file.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: Anyone got ideas on how to make Gajim aware of plugins in store?

[ng0]

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

Ricardo Wurmus transcribed 0.9K bytes:
> 
> ng0 <ng0@pragmatique.xyz> writes:
> 
> > Do I use native-search-paths? There is no variable
> > which is used in Gajim, so I think maybe I need to
> > include this in the wrapper and add something similar
> > to the native-search-path which would look in
> > ~/.guix-profile/share/gajim/plugins/ for $name-of-plugin
> > to PATH?
> 
> Gajim assumes that there is a single plugin directory, which has to be
> set at configuration time.  This means that you cannot even default it
> to ~/.guix-profile/share/gajim/plugins, because people might use
> different profile directories.
> 
> The best way to fix this is upstream by sending them a patch that would
> make Gajim look for plugins in other directories, either by implementing
> a search path environment variable or by adding a key to the
> configuration file.
> 
> -- 
> Ricardo
> 
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net
> 
> 

I've got this reply on my ticket, so maybe I didn't explain my
problem well enough.
Does someone have an answer that is easy to understand to pass on
(or better: sign up and deal with it upstream)?


Date: Thu, 03 Aug 2017 14:58:07 +0200
From: Yann Leboulanger <gitlab@dev.gajim.org>
To: ng0
Subject: Re: gajim | plugins: location: implement either search-path or option for configuration file (#8682)

Gajim looks in 2 places for plugins:
 - $XDG_DATA_HOME/gajim/plugins
  - GAJIM_INSTALL_PATH/plugins (/usr/share/gajim/plugins for example)

So you can set $XDG_DATA_HOME to something else. Isn't it enough?



Reply to this email directly or view it on GitLab: https://dev.gajim.org/gajim/gajim/issues/8682#note_180384
You're receiving this email because of your account on dev.gajim.org.


-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Anyone got ideas on how to make Gajim aware of plugins in store?

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]

ng0 <ng0@infotropique.org> writes:

> Ricardo Wurmus transcribed 0.9K bytes:
>> 
>> ng0 <ng0@pragmatique.xyz> writes:
>> 
>> > Do I use native-search-paths? There is no variable
>> > which is used in Gajim, so I think maybe I need to
>> > include this in the wrapper and add something similar
>> > to the native-search-path which would look in
>> > ~/.guix-profile/share/gajim/plugins/ for $name-of-plugin
>> > to PATH?
>> 
>> Gajim assumes that there is a single plugin directory, which has to be
>> set at configuration time.  This means that you cannot even default it
>> to ~/.guix-profile/share/gajim/plugins, because people might use
>> different profile directories.
>> 
>> The best way to fix this is upstream by sending them a patch that would
>> make Gajim look for plugins in other directories, either by implementing
>> a search path environment variable or by adding a key to the
>> configuration file.
>> 
>> -- 
>> Ricardo
>> 
>> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
>> https://elephly.net
>> 
>> 
>
> I've got this reply on my ticket, so maybe I didn't explain my
> problem well enough.
> Does someone have an answer that is easy to understand to pass on
> (or better: sign up and deal with it upstream)?

[...]

> Date: Thu, 03 Aug 2017 14:58:07 +0200
> From: Yann Leboulanger <gitlab@dev.gajim.org>
> To: ng0
> Subject: Re: gajim | plugins: location: implement either search-path or option for configuration file (#8682)
>
> Gajim looks in 2 places for plugins:
>  - $XDG_DATA_HOME/gajim/plugins
>   - GAJIM_INSTALL_PATH/plugins (/usr/share/gajim/plugins for example)
>
> So you can set $XDG_DATA_HOME to something else. Isn't it enough?

I went ahead and looked at the source:

https://dev.gajim.org/gajim/gajim/blob/master/gajim/common/configpaths.py#L67-106

It looks like what we want is PLUGINS_BASE to resolve to
"$GAJIM_PLUGIN_PATH/share/gajim/plugins". A more upstream-friendly way
might be to add another gajimpath, say PLUGINS_PATH, and add it here:

https://dev.gajim.org/gajim/gajim/blob/master/gajim/common/gajim.py#L72

Would you like to try it?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Anyone got ideas on how to make Gajim aware of plugins in store?

[ng0]

[-- Attachment #1: Type: text/plain, Size: 2564 bytes --]

Marius Bakke transcribed 2.7K bytes:
> ng0 <ng0@infotropique.org> writes:
> 
> > Ricardo Wurmus transcribed 0.9K bytes:
> >> 
> >> ng0 <ng0@pragmatique.xyz> writes:
> >> 
> >> > Do I use native-search-paths? There is no variable
> >> > which is used in Gajim, so I think maybe I need to
> >> > include this in the wrapper and add something similar
> >> > to the native-search-path which would look in
> >> > ~/.guix-profile/share/gajim/plugins/ for $name-of-plugin
> >> > to PATH?
> >> 
> >> Gajim assumes that there is a single plugin directory, which has to be
> >> set at configuration time.  This means that you cannot even default it
> >> to ~/.guix-profile/share/gajim/plugins, because people might use
> >> different profile directories.
> >> 
> >> The best way to fix this is upstream by sending them a patch that would
> >> make Gajim look for plugins in other directories, either by implementing
> >> a search path environment variable or by adding a key to the
> >> configuration file.
> >> 
> >> -- 
> >> Ricardo
> >> 
> >> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> >> https://elephly.net
> >> 
> >> 
> >
> > I've got this reply on my ticket, so maybe I didn't explain my
> > problem well enough.
> > Does someone have an answer that is easy to understand to pass on
> > (or better: sign up and deal with it upstream)?
> 
> [...]
> 
> > Date: Thu, 03 Aug 2017 14:58:07 +0200
> > From: Yann Leboulanger <gitlab@dev.gajim.org>
> > To: ng0
> > Subject: Re: gajim | plugins: location: implement either search-path or option for configuration file (#8682)
> >
> > Gajim looks in 2 places for plugins:
> >  - $XDG_DATA_HOME/gajim/plugins
> >   - GAJIM_INSTALL_PATH/plugins (/usr/share/gajim/plugins for example)
> >
> > So you can set $XDG_DATA_HOME to something else. Isn't it enough?
> 
> I went ahead and looked at the source:
> 
> https://dev.gajim.org/gajim/gajim/blob/master/gajim/common/configpaths.py#L67-106
> 
> It looks like what we want is PLUGINS_BASE to resolve to
> "$GAJIM_PLUGIN_PATH/share/gajim/plugins". A more upstream-friendly way
> might be to add another gajimpath, say PLUGINS_PATH, and add it here:
> 
> https://dev.gajim.org/gajim/gajim/blob/master/gajim/common/gajim.py#L72
> 
> Would you like to try it?

Thanks!

No, I'd rather want someone else to do this because I have too much
to do currently.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]