Change Details

We decided to move the C++ bindings, Qt bindings and Python bindings out of the gpgme repository into separate repositories. This will likely be done after the next release of gpgme. Even though we'll keep ABI compatibility we will bump the major version to 2. The separation of the three bindings from gpgme has been prepared in {T7110}.

We decided to move the C++ bindings, Qt bindings and Python bindings out of the gpgme repository into separate repositories. This will likely be done after the next release of gpgme. Even though we'll keep ABI compatibility we will bump the major version to 2. The separation of the three bindings from gpgme has been prepared in {T7110}. >>! In T7110#190298, @werner wrote: > Okay. Let us split it into different tarballs and repos. We will bump the gpgme core version to 2.0 to indicate this split despite that there will be non-ABI/API incompatibility. C++, Qt, Python will then go into separate projects. The old common List stuff will be kept in gpgme core for now. The gpgme core sticks with autoconf stuff but for C++ and Qt cmake style will be used instead.

We decided to move the C++ bindings, Qt bindings and Python bindings out of the gpgme repository into separate repositories. This will likely be done after the next release of gpgme. Even though we'll keep ABI compatibility we will bump the major version to 2. The separation of the three bindings from gpgme has been prepared in {T7110}. >>! In T7110#190298, @werner wrote: > Okay. Let us split it into different tarballs and repos. We will bump the gpgme core version to 2.0 to indicate this split despite that there will be non-ABI/API incompatibility. C++, Qt, Python will then go into separate projects. The old common List stuff will be kept in gpgme core for now. The gpgme core sticks with autoconf stuff but for C++ and Qt cmake style will be used instead.