-
-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign MacVim Builds #517
Comments
I don't have Apple Developer Program. |
My work laptop is locked down, so no possible way to use MacVim. |
Reopen for investigation. |
I'm opposed to this if it means we won't be able to build it on our own machines without a Developer Cert. |
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. |
Could we accept a limited amount of donations for this purpose? |
I thought about it but I have already purchased an account. Maybe I’ll do it next year for renewal. |
Vim patch 8.1.873 Targets macOS 10.8+ General: - MacVim binary is now signed by a Developer ID (macvim-dev#517). This makes it easier to download and run the app without security warnings. - This also fixes an issue where invoking external programs via `:!open` was slow in Mojave. macvim-dev#763 - Ruby version has been updated from 2.5 to 2.6. Fixes: - Scrollbars are no longer misplaced when resizing window macvim-dev#827 - Fix rendering performance issues for commands (e.g. `:version`, `:echo`, or `:!`) that echo text in Mojave macvim-dev#840 - MacVim now properly asks for permission to use AppleEvent (ODB Editor Suite requires that to work) macvim-dev#822 - Fix borderless window mode in pre-Mojave versions macvim-dev#828 Script interfaces have compatibility with these versions: - Lua 5.3 - Perl 5.18 - Python2 2.7 - Python3 3.7 - Ruby 2.6
Latest release (https://github.com/macvim-dev/macvim/releases/tag/snapshot-154) now signs the app. |
It looks like MacVim.app is not signed. I get "MacVim.app can't be opened because it is from an unidentified developer."
As this is a first barrier for new users, please sign the binary.
The text was updated successfully, but these errors were encountered: