<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/doc, branch gpgme-1.12.0</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.12.0</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.12.0'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-10-05T13:14:58Z</updated>
<entry>
<title>build: Move config.h to conf/config.h</title>
<updated>2018-10-05T13:14:58Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2018-10-05T13:14:58Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=ecfa48fffa93f3d1b66354d2d46872ff614c4a68'/>
<id>urn:sha1:ecfa48fffa93f3d1b66354d2d46872ff614c4a68</id>
<content type='text'>
* conf/: New dir.
* configure.ac (AC_CONFIG_HEADER): Move header to conf dir.
* doc/Makefile.am (mkdefsinc): Adjust rule.
* lang/python/Makefile.am (copystamp): Ditto.
--

C++ uses those stupid files without a suffix and thus the new standard
header &lt;version&gt; as included by newer other libc++ versions may
conflict with the VERSION file in out top directory.   This change
should solve the problem.

GnuPG-bug-id: 4168
Signed-off-by: Werner Koch &lt;wk@gnupg.org&gt;
</content>
</entry>
<entry>
<title>python: makefiles</title>
<updated>2018-10-04T11:10:46Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-10-04T11:10:46Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=f3fc73738264d21baf0e9b49fdd5cb67faa11d31'/>
<id>urn:sha1:f3fc73738264d21baf0e9b49fdd5cb67faa11d31</id>
<content type='text'>
* doc/Makefile.am: Removed a bit I forgot about.
* Renamed lang/python/docs to lang/python/doc bvecause apparently
  automake cares about that too.
* Decided to be extra explicit in the manifest because if I don't then
  all sorts of things get deleted ... like lang/python
* Tested on an external linux system just in case my osx workstation
  introduces too much weirdness.

Tested-by: Ben McGinnes &lt;ben@adversary.org&gt;
Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>docs: pre-python preparation</title>
<updated>2018-10-03T15:42:12Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-10-03T15:42:12Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=b2802053192ba0000866b145b715a557d34ed0eb'/>
<id>urn:sha1:b2802053192ba0000866b145b715a557d34ed0eb</id>
<content type='text'>
* doc/Makefile.am: removed the python howto from this file, restoring
  it to just the main project and the newer .js files.
* deleted: doc/gpgme-python-howto.texi
* renamed the Short_History.org file to short-history.org to keep the
  naming conventions similar.
* All the Python files can (and should) live together.
</content>
</entry>
<entry>
<title>python bindings: CPython order</title>
<updated>2018-10-02T20:58:51Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-10-02T20:58:51Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=23894ac9a96081428a590791010ca8beebaf6f9f'/>
<id>urn:sha1:23894ac9a96081428a590791010ca8beebaf6f9f</id>
<content type='text'>
* Changed the order of python versions the configure/make process
  checks for, placing Python 3.7 ahead of 3.6.
* Updated the HOWTO documentation to reflect this change.

Tested-by: Ben McGinnes &lt;ben@adversary.org&gt;
Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>core: add experimental GPGME_EXPORT_MODE_NOUID.</title>
<updated>2018-10-02T09:18:00Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2018-10-02T09:18:00Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=7b861945fdc71fd3c82c91f824172dadd2220fa0'/>
<id>urn:sha1:7b861945fdc71fd3c82c91f824172dadd2220fa0</id>
<content type='text'>
* src/gpgme.h.in (GPGME_EXPORT_MODE_NOUID): New.
* src/export.c (export_start): Adjust option check.
* src/engine-gpg.c (export_common): Implement option.

Signed-off-by: Werner Koch &lt;wk@gnupg.org&gt;
</content>
</entry>
<entry>
<title>docs: python bindings</title>
<updated>2018-09-30T16:10:03Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-09-30T16:10:03Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=76bdfabb057f4ffc56beee15b48d8fa836ba7cce'/>
<id>urn:sha1:76bdfabb057f4ffc56beee15b48d8fa836ba7cce</id>
<content type='text'>
* Tightened up the docs a little bit, updated the "what's new"
  section, dropped the "-draft" version in preparation for GPGME
  1.12.0's release.
* Exported another .texi version (and updated the draft copies to this
  commit (which ought to be 1.11.1-beta313).

Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>docs: a typographical two-step</title>
<updated>2018-09-25T00:17:39Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-09-25T00:17:39Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=b625258d54782040195cc5ad3b255685af6f6c4e'/>
<id>urn:sha1:b625258d54782040195cc5ad3b255685af6f6c4e</id>
<content type='text'>
* Sometimes you really do need or want punctuation in a heading, but
  ideally without something else generating whitespace and other
  annoyances to go with it.
* Trying a real decimal point instead.

Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>docs and examples: python bindings</title>
<updated>2018-09-24T23:59:31Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-09-24T23:59:31Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=62e4e2cb5edb09183b9f9d448f992fe65cb6db85'/>
<id>urn:sha1:62e4e2cb5edb09183b9f9d448f992fe65cb6db85</id>
<content type='text'>
* Woumd up the "what's new" section.
* Added an example for sending a key to the keyservers via hkp4py.
* Updated the export key code to use a more complete check for the
  $GNUPGHOME location.
* Expanded on the installation and reinstallation troubleshooting
  section.

Tested-by: Ben McGinnes &lt;ben@adversary.org&gt;
Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>docs: python bindings howto</title>
<updated>2018-09-24T18:32:13Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-09-24T18:32:13Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=e9da4d97107b40a48583775df34783f07be5dfdb'/>
<id>urn:sha1:e9da4d97107b40a48583775df34783f07be5dfdb</id>
<content type='text'>
* Added a What's New section to summarise changes since the last
  release.  There have been quite a few and some attention does need
  to be drawn to some of them.
* Confirming certain issues with some platform builds, especially
  BSD/OSX vs. Linux issues which will need to update the installation
  troubleshooting guides.
</content>
</entry>
<entry>
<title>docs and examples: python bindings howto</title>
<updated>2018-09-23T09:36:54Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-09-23T09:36:54Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=b12b2cc99621fe32a2d698ce7f091f3225f35bd0'/>
<id>urn:sha1:b12b2cc99621fe32a2d698ce7f091f3225f35bd0</id>
<content type='text'>
* Added more comprehensive examples using hkp4py and added a couple
  more example scripts for protonmail.

Tested-by: Ben McGinnes &lt;ben@adversary.org&gt;
Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
</feed>
