Ok, cool.
Ah, just found http://wiki.inkscape.org/wiki/index.php/Roadmap
It looks like doing this work on Github and (maybe) getting Travis CI working would be useful work-ahead, and not just a side-distraction for tinkering on the Mac build. I’d rather it didn’t come down to people relying on me to create and release builds ;-)
Building on Atsuyoshi’s work, I think there’s one issue that is critical to fix before calling it a generally usable release: figuring out what to do about python and libxml support. Without it extensions probably won’t work.
(I’d also like to see uniconvertor added to, but that might be quite a bit more work.)
Julian
On Wed, 2017-02-01 at 15:21 -0500, Julian Rendell wrote:
> 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.)
Our publishing procedure is fairly simple.
1. Have a user account on inkscape.org
2. Modify your account with your name, picture and gpg key (a fake key
is ok, it must exist for you to upload an md5)
3. Contact the website administrator to increase your quota from 10MB
4. Upload your DMG along with an md5 or gpg signature
5. Inform people on the inkscape mailing list to do any final testing
of the download. Provide a link. The files will be automatically cached
by our CDN.
6. Change the website's CMS pages with the new links and announce more
widely.
Best Regards, Martin Owens
Website Administrator