Dipping my toes into the inkscape-devel list.

I think there’s need for an “official” MacOS build for Inkscape.

e.g. this message: https://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/9B4B6CD283CF47FA9B608BCDF0E95994%40brynnPC/#msg35637605

There are a few non-core(???) developers/advanced users trying to get MacOS packaging working again; both on this thread and e.g. https://sourceforge.net/p/inkscape/mailman/message/35584561/

(There’s a great gist with a working procedure, including patches linked in Atsuyoshi’s post: https://gist.github.com/atuyosi/ab5499a176b0b456bca98c44e2775cbb)

Question for core team:

If the packaging is figured out, does the Inkscape team have the resources to create and publish a Mac binary that can be hosted the same as the Windows/Linux builds? (I’m not sure what the CI/build infrastructure is for Inkscape.)

Extra: could the builds be signed so that they don’t raise security warnings?

For Kirk, Tim, Brynn, Windell, Chris, Lyndsy, Atsuyoshi- do you want to work together to try and solve this?

I’m most comfortable with git/github, and a quick google reveals there are some git to/from bzr tools (e.g. https://github.com/felipec/git-remote-bzr)

My suggestion would be to setup a git repo/project and manually pull in the latest 0.92 branch. Then pull in Atsuyoshi’s work, get it working locally, then in CI (travis?) In the interim, packages could be hosted as releases on the GitHub project page; hopefully the Inkscape project would be able to eventually pick up this work and make the github repo obsolete. (I’d suggest deleting the github repo at that point. No need for historic projects to add to user confusion ;-) )

I’m also happy to see it hosted elsewhere.

Let me know if you’d be interested in this and I’ll set up a repo/try to participate in figuring out the patches.

Thanks everyone!