unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Anyone got ideas on how to make Gajim aware of plugins in store?
Date: Sat, 12 Aug 2017 13:55:59 +0000	[thread overview]
Message-ID: <20170812135559.zxhlql7wco3jtkwv@abyayala> (raw)
In-Reply-To: <87bmnk3ogu.fsf@fastmail.com>

[-- 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 --]

      reply	other threads:[~2017-08-12 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 10:33 Anyone got ideas on how to make Gajim aware of plugins in store? ng0
2017-06-12 18:17 ` Arun Isaac
2017-06-13 20:38 ` Ricardo Wurmus
2017-08-12 10:30   ` ng0
2017-08-12 13:28     ` Marius Bakke
2017-08-12 13:55       ` ng0 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170812135559.zxhlql7wco3jtkwv@abyayala \
    --to=ng0@infotropique.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).