From: Efraim Flashner <efraim@flashner.co.il>
To: phodina <phodina@protonmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Plugins for Kicad and other programs
Date: Sun, 3 Oct 2021 20:37:11 +0300 [thread overview]
Message-ID: <YVnqRxpXTyyWLRRF@3900XT> (raw)
In-Reply-To: <K6Sovf0C522y_GQOkvVhSPGGRZYa_TW_A6SjZNcn9-lId-eKeSbFEPRByFLz4ONQ373PXeWdpd_34MA8iWXsgxUYC7MqpTZV0JMcSiYrcQc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2668 bytes --]
On Sun, Oct 03, 2021 at 11:31:40AM +0000, phodina via wrote:
> Hi Guix,
>
> Lots of programs now allow users to extend their features through plugins.
> On non Guix distros where the user does not have the root priviledges they place
> the the content of their plugin in the configuration directory in home directory.
>
> Here's example for Kicad:
> ~/.kicad_plugins/
> ~/.kicad/scripting/
> ~/.kicad/scripting/plugins/
>
> To further complicate things they can have their own plugin manager (e.g. Freecad).
>
> In some cases they contain just some raw data or configs. However, large amount has
> some code embedded like shell scripts, python which needs special handling on Guix.
>
> Therefore my question is how to integrate them?
>
> What I propose is with the merge of home services [2], there is now possibility to:
>
> - create package defintion of the plugin
> - create home service that will link the plugin into the correct location
> within the home dir
>
> There is also an alternative.
> I searched the Kicad forum for plugin installation and installation into system dirs
> (under /usr) is not recommended [2]. The plugin could be linked into the plugin
> location under the /gnu/store/xxx-package. This could be done by inheriting kicad
> package and adding the plugins to the input. That approach wouldn't be very flexible,
> as it would create to many package combinations.
>
> Also I never installed plugins into system directories on distibutions used before
> Guix system so I don't know if it would work.
>
> [1] commit 6ae4644984608b7eff7ab54d3a5787c661d85b2e
> [2] https://forum.kicad.info/t/plugin-location-ubuntu-refresh-solved/24396
Following down that thread, I came across this other bit too:
Can you follow the instruction in the document you linked to:
Open Tools -> Scripting Console in pcbnew
type import pcbnew; print pcbnew.PLUGIN_DIRECTORIES_SEARCH
What does it tell?
v3xX
Aug 2020
/usr/share/kicad/scripting
/usr/share/kicad/scripting/plugins
/home//.config/kicad/scripting
/home//.config/kicad/scripting/plugins
/home//.kicad_plugins
/home//.kicad/scripting
/home//.kicad/scripting/plugins
it looks like it should search in this folders.
so it looks like kicad could have a search-path of 'share/kicad' or
'share/kicad/scripting' and the plugins installed to
%out/share/kicad/scripting for each plugin.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-04 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 11:31 Plugins for Kicad and other programs phodina via
2021-10-03 17:37 ` Efraim Flashner [this message]
2021-10-04 17:42 ` phodina
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=YVnqRxpXTyyWLRRF@3900XT \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=phodina@protonmail.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.
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).