[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Plugin Package Paths

From: Peter Polidoro
Subject: Plugin Package Paths
Date: Wed, 13 Sep 2023 10:01:16 -0400
User-agent: mu4e 1.10.5; emacs 28.2

What is the proper way to package plugins when a packaged program searches for them in the executable path rather than the profile path?

I would like to package plugins for two programs, kicad and freecad, and they both search for plugins by first finding the path of the executable. Freecad uses /proc/self/exe and kicad uses wxStandardPaths::GetExecutablePath. This seems to cause them to look for plugins in the package path in the store rather than the profile path.

What is the proper way of handling this when packaging plugins? Should the package of the main program modify the source code to find the path of the executable using the environment variable GUIX_ENVIRONMENT rather than /proc/self/exe or wxStandardPaths::GetExecutablePath? Or can these calls be tricked with hard links somehow? Or is there some other better way of dealing with this?

These programs also search for plugins in the user home directory, but would using those require using system containers?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]