[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inkscape export errors
From: |
Ludovic Courtès |
Subject: |
Re: Inkscape export errors |
Date: |
Wed, 21 Oct 2020 17:59:57 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Saluton!
Ekaitz Zarraga <ekaitz@elenq.tech> skribis:
>> You would then need to include this variant of ‘inkscape’ alongside
>> ‘python’ so that ~/.guix-profile/etc/profile sets ‘PYTHONPATH’
>> accordingly.
>>
>> A better fix would be to use ‘wrap-program’ to wrap ‘inkscape’ such that
>> ‘PYTHONPATH’ always points to ‘python-lxml’. There are several examples
>> of packages that do that.
>
> Yes, kind of the same change I did on Icecat for the WebGL support.
> This is going to create a shell script that sets the environment
> variables and then call the actual binary, right?
Exactly.
> Why isn't inkscape detecting python-lxml if I can load it from the python
> shell?
> Does this mean the package's environment is being cleaned by someone else?
> Why does Thorsten's (in the thread) inkscape detect lxml and
> mine doesn't?
> Isn't this supposed to be reproducible?
Heheh. To make sure you’re both testing the same thing, use:
guix environment --pure --ad-hoc inkscape -- inkscape
That will avoid interference from the environment.
Ludo’.