By the way,
> GPG Suite could update to 2.1.x tomorrow and bork a bunch of formulae
Having used GPG Suite for a few years, I'd say (with >95% confidence) it won't be updated to 2.1.x until the very last minute. Not really blaming them, but they've always been playing catch-up, apparently due to lack of resources.
> It's a valid concern but at some point this change will have to go through and some sacrifices will need to be made to get there.
I never tried to stop this. All I'm proposing is an additional sentence in the caveats (which is feature-length already).
> How about after every installation of software that has a data store of some kind
Care to give an example of a pair of notable, non-version packages in Homebrew/Caskroom's official repositories that require conflicting formats of the exact same data store?
Okay, created support ticket https://gpgtools.tenderapp.com/discussions/problems/51244. (Code is at https://github.com/GPGTools/MacGPG2, but issue tracker isn't enabled.)
In the meantime, "my practical suggestion of not having both brewed gpg 2.1.x (assuming it will land soon) and GPG Suite installed at the same time" still stands.
All I know about "2.0 EOL" is from https://www.gnupg.org/download/index.html:
> GnuPG modern (2.1) is the brand new version with enhanced features like support for Elliptic Curve Cryptography. It will eventually replace the current stable (2.0).
"Eventually" can mean anything, hence nothing. Have you heard of a more concrete plan? Or are you suggesting that I torture a plan out of the GPG team first?
Nevertheless, I'm not sure how that suggestion conflicts with my practical suggestion of not having both brewed gpg 2.1.x (assuming it will land soon) and GPG Suite installed at the same time. You simply can't use both without messing up, unless you have separate `GNUPGHOME`s, which is unlikely.
Also note that GPG Suite can be installed via `brew-cask` (`brew cask install gpgtools`) so you can't tie up your hands and say "none of our business".