Tracking the bleeding edge can be problematic, suggesting using some defined snapshot of them, possibly even shipping them ourselves in the image. Gtk and assorted libs are moving targets, version-wise. Many of our current bug reports and discussions are about these legacy packages some issues will still be relevant with a native package, some won't. There have been several different packaging solutions, including through MacPorts and HomeBrew. Legacy packages include the various XQuartz (X11-based) packages currently in use for distributing the 0.92x version of Inkscape. Breakdownįrom what I have gathered, it sounds like we can break this problem up into a few discrete pieces: (1) Legacy package maintenance We don't need to link every bug related to Mac, just issues involving the packaging itself, feature development needs, and severely critical bugs. This is a master issue for outlining the problem space and linking all bug reports relevant to creation of a native Mac package. Since it will still use Gtk this isn't 'Native' in the truest sense of the word, but it will adhere closely to the standard Mac user experience. This means we need to compile Inkscape with Quartz but without X11 and against Gtk3 instead of Gtk2, with current Inkscape master. This is a top request from many of our users and sponsors.

Ultimately, we want signed DMG (non-X) releases of Inkscape 1.0.

How to install inkscape on mac 2019