GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

* configure.ac: Bump up LIBGPGME_LT_REVISION.

Browse Source 
(NEED_GPG_VERSION): Set to 1.2.0
(NEED_GPGSM_VERSION): Set to 0.9.2
This commit is contained in:
Werner Koch 2002-10-15 10:00:49 +00:00
parent 8e2da19a1b
commit d7474c4089
5 changed files with 20 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ChangeLog
View File

@ -1,3 +1,11 @@
2002-10-15 Werner Koch <wk@gnupg.org>
Released 0.3.12
* configure.ac: Bump up LIBGPGME_LT_REVISION.
(NEED_GPG_VERSION): Set to 1.2.0
(NEED_GPGSM_VERSION): Set to 0.9.2
2002-09-20 Werner Koch <wk@gnupg.org> 2002-09-20 Werner Koch <wk@gnupg.org>
Released 0.3.11. Released 0.3.11.

7
NEWS
View File

@ -1,6 +1,11 @@
Noteworthy changes in version 0.3.12 (unreleased) Noteworthy changes in version 0.3.12 (2002-10-15)
------------------------------------------------- -------------------------------------------------
* Fixed some bux with key listsings.
* The development has been branched to clean up some API issues.
This 0.3 series will be kept for compatibility reasons; so do don't
expect new features.
Noteworthy changes in version 0.3.11 (2002-09-20) Noteworthy changes in version 0.3.11 (2002-09-20)
------------------------------------------------- -------------------------------------------------

11
README
View File

@ -6,19 +6,14 @@
If you want to hack on it, start with one of the `tests/gpg/t-foo' If you want to hack on it, start with one of the `tests/gpg/t-foo'
programs. programs.
For support of the OpenPGP protocol (default), you need the latest CVS For support of the OpenPGP protocol (default), you need at least GnuPG
version of GnuPG 1.0, see `http://www.gnupg.org/cvs-access.html'. 1.2.0.
You need at least GnuPG 1.0.7, but don't use a 1.1.x version.
If configure can't find the `gpg' binary in your path, you can specify 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. the location with the --with-gpg=/path/to/gpg argument to configure.
For support of the CMS (Cryptographic Message Syntax) protocol, you For support of the CMS (Cryptographic Message Syntax) protocol, you
need the latest CVS version of GpgSM, module name `newpg', at need at least newpg 0.9.2
`:pserver:anoncvs@cvs.gnupg.org:/cvs/aegypten'.
You need at least GpgSM 0.3.8.
If configure can't find the `gpgsm' binary in your path, you can If configure can't find the `gpgsm' binary in your path, you can
specify the location with the --with-gpgsm=/path/to/gpgsm argument to specify the location with the --with-gpgsm=/path/to/gpgsm argument to

3
TODO
View File

@ -68,9 +68,6 @@ Hey Emacs, this is -*- outline -*- mode!
** Make sure everything is cleaned correctly (esp. test area). ** Make sure everything is cleaned correctly (esp. test area).
Bugs reported by Stephane Corthesy: Bugs reported by Stephane Corthesy:
> BTW, here's another bug: it it not possible to retrieve fingerprints
> for subkeys
--> This seems to work now (wk 2002-08-20)
> In GpgmeRecipients, would it be possible to provide a function which > In GpgmeRecipients, would it be possible to provide a function which
> would return the validity assigned to a name contained in the > would return the validity assigned to a name contained in the

6
configure.ac
View File

@ -30,9 +30,9 @@ AC_INIT(gpgme, 0.3.12, [bug-gpgme@gnupg.org])
# #
LIBGPGME_LT_CURRENT=9 LIBGPGME_LT_CURRENT=9
LIBGPGME_LT_AGE=3 LIBGPGME_LT_AGE=3
LIBGPGME_LT_REVISION=2 LIBGPGME_LT_REVISION=3
NEED_GPG_VERSION=1.0.7 NEED_GPG_VERSION=1.2.0
NEED_GPGSM_VERSION=0.3.8 NEED_GPGSM_VERSION=0.9.2
############################################## ##############################################
AC_PREREQ(2.52) AC_PREREQ(2.52)
AC_REVISION($Revision$) AC_REVISION($Revision$)