You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MacVim is open-sourced so you can always still build it yourself :). We also still need to support Homebrew builds (which builds from source) of course.
Part of the investigation is coming up with a satisfactory way to enable code signing in the build system (Travis CI) while keeping the main Xcode project in the repo pristine.
I do think for distributed binary we should try to sign it. Sparkle (our update system) already checks for a code signature but it’s nice to have an Apple-signed binary for peace of mind (not to mention Apple is heavily encouraging this which makes the first-time user experience quite annoying otherwise).
As a side note, #763 is related to this for some weird reason. I suspect the fact that MacVim is unsigned causes some slow validation path to trigger in Mojave when calling external application.
Well, Hammerspoon is also open-source, but if I want to build it from source and not have it be a console-spamming debug build, I have to make a self-signed cert and "sign" it with that. What a PITA; I hope this never happens to MacVim.
I think this is because Hammerspoon requires system permission which would be annoying if you don’t self-sign the app. So a little bit of a different circumstance from MacVim.
Activity
splhack commentedon Jul 23, 2017
I don't have Apple Developer Program.
EarthCitizen commentedon Dec 1, 2018
My work laptop is locked down, so no possible way to use MacVim.
ychin commentedon Dec 4, 2018
Reopen for investigation.
chdiza commentedon Dec 4, 2018
I'm opposed to this if it means we won't be able to build it on our own machines without a Developer Cert.
ychin commentedon Dec 4, 2018
MacVim is open-sourced so you can always still build it yourself :). We also still need to support Homebrew builds (which builds from source) of course.
Part of the investigation is coming up with a satisfactory way to enable code signing in the build system (Travis CI) while keeping the main Xcode project in the repo pristine.
I do think for distributed binary we should try to sign it. Sparkle (our update system) already checks for a code signature but it’s nice to have an Apple-signed binary for peace of mind (not to mention Apple is heavily encouraging this which makes the first-time user experience quite annoying otherwise).
As a side note, #763 is related to this for some weird reason. I suspect the fact that MacVim is unsigned causes some slow validation path to trigger in Mojave when calling external application.
chdiza commentedon Dec 4, 2018
Well, Hammerspoon is also open-source, but if I want to build it from source and not have it be a console-spamming debug build, I have to make a self-signed cert and "sign" it with that. What a PITA; I hope this never happens to MacVim.
ychin commentedon Dec 5, 2018
I think this is because Hammerspoon requires system permission which would be annoying if you don’t self-sign the app. So a little bit of a different circumstance from MacVim.
eirnym commentedon Dec 29, 2018
Could we accept a limited amount of donations for this purpose?
ychin commentedon Dec 30, 2018
I thought about it but I have already purchased an account. Maybe I’ll do it next year for renewal.
MacVim Snapshot 154
ychin commentedon Feb 4, 2019
Latest release (https://github.com/macvim-dev/macvim/releases/tag/snapshot-154) now signs the app.