

This tutorial was tested on Linux Mint 17.2. So I decided to use a chroot environment, which is the best compromise for me. I also didn’t want to use a virtual machine, as that would cost even more disk space than the chroot and be slower. I did not want to compile myself, but use the version offered in the ppa for Ubuntu at launchpad. Inkscape’s development version, unfortunately, does not use a different package name and directory naming structure from the released version - so directly installing the trunk version from the ppa on my Linux Mint would overwrite the stable version (which I want to keep!). or you can use a chroot environment, which allows you to switch to some kind of ‘separate operating system file tree’ inside your current operating system.you could statically link the libraries (also needs compiling).you can compile Inkscape so it uses different paths for its libraries.you could use a container (e.g. docker).you could use a virtual machine (e.g. VirtualBox).you could be lucky and the development version uses a different naming structure (e.g.There are several options how to install the development version of Inkscape (or any other program) in parallel with the stable version on Linux:
