From: Simon Tatham Date: Wed, 27 Oct 2021 17:10:24 +0000 (+0100) Subject: Work around inkscape accessing its environment. X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~sgtatham/git?a=commitdiff_plain;h=2a61baa7890314a169dd6114b6e99b70768b330a;p=chroma-debian.git Work around inkscape accessing its environment. Bug #997904 points out that even this command-line use of Inkscape will try to write to ~/.config/inkscape (in order to create a default one if it's not already there), and also, will try to initialise GDK (especially strange in the absence of an X or Wayland server, where it will try to fall back to the HTTP-server based Broadway backend). Worked around by resetting $HOME to the build directory, where it doesn't matter if we create an Inkscape config directory, and by setting GDK_BACKEND to the empty string, which seems to inhibit it trying to actually launch any backends. --- diff --git a/debian/rules b/debian/rules index f64a235..7df1895 100755 --- a/debian/rules +++ b/debian/rules @@ -8,5 +8,5 @@ override_dh_auto_configure: override_dh_auto_build-arch: dh_auto_build - cd resources && ./make-graphics.sh + cd resources && env HOME=$$PWD GDK_BACKEND= ./make-graphics.sh cd resources && ../debian/make-debian-icons.py