3 ms·
> After every MacOS update, GPG stops working. That's just not helping to drive adoption and it's just not acceptable IMHO. I agree, apple should stop breaking
by saosebastiao 10y ago
> After every MacOS update, GPG stops working. That's just not helping to drive adoption and it's just not acceptable IMHO.
I agree, apple should stop breaking users' code with every release.
- atonse 10y agoApple has a 4-5 month beta period between when they release the OS to developers, and to the public.
- joshka 10y agoI recall seeing somewhere that there was a change in things between the Sierra betas and the final release that affected GPGTools. I can't find the post / thread unfortunately. The note at [1] is as close as I can find. > Apple's changes are even more substantial this time around, then they were in the last releases. > In addition they're now using more blocks instead of methods in some places, which means that we can no longer simply hook into them, but have to completely re-implement some internal functionality of Mail, to place our code in between. > We've already rewritten a lot of parts of GPGMail and hope to have a first beta in the next few weeks. [1]: https://github.com/GPGTools/GPGMail/commit/f871731f5762cb72e6262f1d790e8dbad5319398#commitcomment-19943799 https://github.com/GPGTools/GPGMail/commit/f871731f5762cb72e...
- gmgorange 10y agoMaybe the GPG Suite folks should stop writing the integration in such a fragile manner. Maybe they should use the time the upcoming macOS is in developer/public beta to fix any issues ahead of the release? Maybe GPG Suite shouldn't be a thing given the lack of interest and support?