diff options
| author | Jeffrey Stedfast <jestedfa@microsoft.com> | 2017-07-13 12:23:55 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-07-13 12:23:55 -0400 |
| commit | ee8c9f4b3276e7f8f2ecfc4a40489353efa549d8 (patch) | |
| tree | c1c34c6d416d6405cb66e0eb42acf4e129285324 /PORTING | |
| parent | d4a200802ca8c5fa0dd60d66cbe7d680077adaa0 (diff) | |
| parent | 80e7e96e26c1f0fe44b9a0237210f4d1298817c5 (diff) | |
| download | gmime-ee8c9f4b3276e7f8f2ecfc4a40489353efa549d8.tar.gz | |
Merge pull request #7 from dkg/gpgpath
PORTING: No way to explicitly set the path to gpg as of gmime 3.0
Diffstat (limited to 'PORTING')
| -rw-r--r-- | PORTING | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -92,6 +92,11 @@ Porting from GMime 2.6 to GMime 3.0 - Removed g_mime_gpg_context_[get,set]_auto_key_retrieve(). +- When using GMimeGpgContext, there is no longer a way to explicitly + set the path to the "gpg" executable. Of course, users can still + use the $PATH environment variable to select any executable named + "gpg" as always. + - Removed g_mime_crypto_context_[get,set]_retrieve_session_key(). This is now handled by passing GMIME_DECRYPT_EXPORT_SESSION_KEY to the g_mime_crypto_context_decrypt() method. |