Subject: PR/32761 CVS commit: pkgsrc/security/gpgme
To: None <,,>
From: Thomas Klausner <>
List: pkgsrc-bugs
Date: 07/19/2006 23:00:07
The following reply was made to PR pkg/32761; it has been noted by GNATS.

From: Thomas Klausner <>
Subject: PR/32761 CVS commit: pkgsrc/security/gpgme
Date: Wed, 19 Jul 2006 22:59:59 +0000 (UTC)

 Module Name:	pkgsrc
 Committed By:	wiz
 Date:		Wed Jul 19 22:59:59 UTC 2006
 Modified Files:
 	pkgsrc/security/gpgme: Makefile distinfo
 	pkgsrc/security/gpgme/patches: patch-ab patch-ac patch-ae patch-ah
 	    patch-ai patch-aj
 Log Message:
 Update to 1.1.0, based on patches provided by George Michaelson
 in PR 32761.
 Noteworthy changes in version 1.1.0 (2005-10-01)
  * You can now configure the backend engine file name and home
    directory to be used, as default and per context.
  * Information about the recipients of an encrypted text is now
    available at decryption time.
  * New status GPGME_STATUS_PLAINTEXT.  This is analyzed by the decrypt
    and verify handlers, the information about the plaintext filename,
    if available is made available in the new field file_name of the
    respective result structure.
  * The code for "automagically detecting the thread library" has been
    removed from libgpgme.  It is deprecated since version 0.4.3.
    Since then, you had to link against libgpgme-pthread for
    applications using pthread and libgpgme-pth for applications using
    GNU Pth.
    The code was removed because it caused compilation problems on
    systems where the pthread.h header from GNU Pth is available in
    addition to the system header (FreeBSD 6 and later for example).
  * There is a new flag for keys and subkeys, is_qualified, which
    indicates if a key can be used for qualified signatures according
    to local government regulations.
  * You can associate a filename with a data object using the new
    function gpgme_data_set_file_name().  This filename will be stored
    in the output when encrypting or signing the data and will be
    returned when decrypting or verifying the output data.
  * You can now set notation data at signature creation with the new
    function gpgme_sig_notation_add().
  * Interface changes relative to the 1.0.3 release:
 gpgme_set_engine_info		NEW
 gpgme_ctx_get_engine_info	NEW
 gpgme_ctx_set_engine_info	NEW
 gpgme_recipient_t		NEW
 gpgme_decrypt_result_t		EXTENDED: New field recipients.
 gpgme_verify_result_t		EXTENDED: New fields pubkey_algo, hash_algo.
 gpgme_decrypt_result_t		EXTENDED: New field plaintext_filename.
 gpgme_verify_result_t		EXTENDED: New field plaintext_filename.
 gpgme_key_t			EXTENDED: New field is_qualified.
 gpgme_subkey_t			EXTENDED: New field is_qualified.
 gpgme_data_get_file_name	NEW
 gpgme_data_set_file_name	NEW
 gpgme_sig_notation_flags_t	NEW
 gpgme_sig_notation_clear	NEW
 gpgme_sig_notation_add		NEW
 gpgme_sig_notation_get		NEW
 To generate a diff of this commit:
 cvs rdiff -r1.42 -r1.43 pkgsrc/security/gpgme/Makefile
 cvs rdiff -r1.22 -r1.23 pkgsrc/security/gpgme/distinfo
 cvs rdiff -r1.3 -r1.4 pkgsrc/security/gpgme/patches/patch-ab
 cvs rdiff -r1.4 -r1.5 pkgsrc/security/gpgme/patches/patch-ac
 cvs rdiff -r1.2 -r1.3 pkgsrc/security/gpgme/patches/patch-ae
 cvs rdiff -r1.1 -r1.2 pkgsrc/security/gpgme/patches/patch-ah \
     pkgsrc/security/gpgme/patches/patch-ai \
 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.