I'm wondering whether gpgme v1 will still be supported? Or it will be abandoned from now on.

We will keep the 1.24 branch for bug fixing. Do you really have a problem with gpgme 2.0? Ist that due to factoring out the c++ and qt bindings? That was actually a long standing request from the KDE community so that they can use their cmake stuff.

We won't fix or extend the gpgme 1.24 branch unless really needed for old projects. it is better to move on to the splitted stuff.

In T7673#201735, @werner wrote:

We will keep the 1.24 branch for bug fixing. Do you really have a problem with gpgme 2.0? Ist that due to factoring out the c++ and qt bindings? That was actually a long standing request from the KDE community so that they can use their cmake stuff.

Thanks for explaining. I’ll of course switch to GPGME 2.0. Since I only use the C API, the fact that the C++ and Qt bindings have been moved to separate repos doesn’t affect me—I can continue using the same interface. I’m asking on behalf of the Homebrew community since my macOS build depends on the Homebrew-maintained gpgme package. My suggestion is to add a “gpgme@2” formula while keeping “gpgme” (v1) intact, so active downstreams can opt into v2 without breaking older builds. The maintainers worry that, if v1 isn’t supported, we’d be forced to ship only v2. If it’s okay, I’d like to quote your explanation to reassure them and keep things moving.

You may refer: https://github.com/Homebrew/homebrew-core/pull/225591