From: Marcus Brinkmann Date: Tue, 22 Jan 2002 16:55:58 +0000 (+0000) Subject: Some small updates. X-Git-Tag: gpgme-0-3-1~36 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=14fe2162770f4dac4b3f67c9b250e7648bd4fcdb;p=gpgme.git Some small updates. --- diff --git a/NEWS b/NEWS index 2cbd981..74f0ab5 100644 --- a/NEWS +++ b/NEWS @@ -9,6 +9,9 @@ * New interface gpgme_op_trustlist_end() to match gpgme_op_keylist_end. + * The CryptPlug modules have been renamed to gpgme-openpgp and + gpgme-smime, and they are installed in pkglibdir by `make install'. + * Interface changes relative to the 0.3.0 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t. diff --git a/README b/README index 9c935b8..892cbf0 100644 --- a/README +++ b/README @@ -15,7 +15,7 @@ If configure can't find the `gpg' binary in your path, you can specify the location with the --with-gpg=/path/to/gpg argument to configure. For support of the CMS (Cryptographic Message Syntax) protocol, you -need the latest CVS version of GpgSM, module name `newpg' at +need the latest CVS version of GpgSM, module name `newpg', at `:pserver:anoncvs@cvs.gnupg.org:/cvs/aegypten'. You need at least GpgSM 0.0.0. @@ -27,7 +27,8 @@ configure. To enable the CryptPlug GPGME PlugIn for both protocols, use the `--enable-gpgmeplug' option to the configure script. `gpgmeplug' is experimental and you should not assume that it will stay with gpgme. -The plug-ins are not installed by `make install'. +The plug-ins are installed by `make install' in `pkglibdir', normally +`PREFIX/lib/gpgme'. Before building the CVS version following the generic install instructions in `INSTALL', you need to set up the build scripts with diff --git a/TODO b/TODO index 8e86f02..10772f7 100644 --- a/TODO +++ b/TODO @@ -7,7 +7,6 @@ ** string representation of non-secret keys and ATTR_IS_SECRET is NULL, which can not be differentiated from the case that it is not representable. -** Agree on gpgme_key_unref or gpgme_key_release and drop the other? ** keylisting mode can go ** api to specify where to search, lokal and/or remote. @@ -18,9 +17,6 @@ * add locking to the key cache? -* Should --delete silently delete secret keys or is there a need for - another flag or a callback? - * GpgmeKey misses GPGME_ATTR_EXPIRE attribute * Add ATTR to return the number of subkeys or uids. @@ -40,6 +36,8 @@ * Operations ** Import, export status handler. +** Should --delete silently delete secret keys or is there a need for + another flag or a callback? * Error Values ** Map ASSUAN error values.