The various inkscape extensions currently in nixpkgs are simple python extensions with no 3rd party python dependencies of their own.
The list of python dependencies available to the inkspace python interpreter is hardcoded here.
As far as I can tell, there’s currently no “good” way of defining a new inkscape extension with its own python dependencies. What’s the best way of accomplishing this? A couple of ideas:
- Tweak pkgs/applications/graphics/inkscape/with-extensions.nix to pull a list of python dependencies from the given
inkscapeExtensionsand thread those through to inkscape itself so it can define the appropriate set of python deps.
- Stop hardcoding a path to Python in the inkscape derivation. Instead, let it look Python up from the
PATH, and carefully wrap inkscape so it has an appropriate
PATHenvironment variable set.
- is a bit unfortunate because it requires recompiling all of inkscape just when a new python dep appears.
I don’t know if there are any serious downsides to 2). Perhaps it wouldn’t play nicely with certain other types of PATH rewriting?