Navigation:
Browse pkgsrc
(this page)| 2004-10-30 12:25:18 by John R. Shannon | Files touched by this commit (1) |
Log message: security/gpgme includes librfuncs/buildink3.mk, but getenv_r was not used because configure fail to detect it. Implemented recomendation from Min Sik Kim to bypass the test. |
| 2004-10-23 17:00:48 by John R. Shannon | Files touched by this commit (6) |
Log message: 1) Updated to gpgme-1.0.1. This is a bug fix release. 2) Added optional support for OpenPGP/MIME and SMIME via gnupg-devel as described here: http://www.gnupg.org/aegypten2/ |
| 2004-10-20 21:09:12 by Julio M. Merino Vidal | Files touched by this commit (3) |
Log message: Update to 1.0.0: * Version 1.0.0! We are proud to present you with a thoroughly tested and stable version of the GPGME library. A big Thank You! to all the people who made this possible. The development will be branched into a stable 1.x.y series and the head. * The gpgme.m4 macro supports checking the API version. Just prepend it to the required version string, separated by a colon. For example, this release has the version "1:1.0.0". The last release to which this version is (mostly) ABI compatible is "1:0.4.2", which is the default required version. |
| 2004-10-03 02:18:40 by Todd Vierling | Files touched by this commit (863) |
Log message: Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include. |
| 2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703) |
Log message: Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST. All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes". |
2004-08-22 19:52:26 by Marc Recht | Files touched by this commit (5) |  |
Log message: update to gpgme-0.9.0 Noteworthy changes in version 0.9.0 (unreleased) ------------------------------------------------ * The type gpgme_key_t has now a new field keylist_mode that contains the keylist mode that was active at the time the key was retrieved. * The type gpgme_decrypt_result_t has a new field "wrong_key_usage" that contains a flag indicating that the key should not have been used for encryption. * Verifying a signature of a revoked key gives the correct result now (GPG_ERR_CERT_REVOKED error code). * Clarified that the error code GPG_ERR_NO_DATA from the decrypt & verify operations still allows you to look at the signature verification result. * Clarified that patterns in keylisting operations have an upper limit, and thus are not suited to list many keys at once by their fingerprint. Also improve the error message if the pattern is too long for the CMS protocol to handle. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_key_t EXTENDED: New field keylist_mode. gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Set the 0.9.0 versions as BUILDLINK_DEPENDS in the buildlink3.mk for the library major version changes. |
| 2004-08-21 12:54:47 by Mark Davies | Files touched by this commit (4) |
Log message: Update to 0.4.7. Noteworthy changes in version 0.4.7 (2004-04-29) ------------------------------------------------ * Correctly initialize the fields expired, revoked, invalid, and disabled in the gpgme_key_t structures. * A bug fix: The flag wrong_key_usage of gpgme_signature_t was accidently of type int instead unsigned int. Noteworthy changes in version 0.4.6 (2004-04-06) ------------------------------------------------ * Bug fixes Noteworthy changes in version 0.4.5 (2004-03-07) ------------------------------------------------ * GPGME is now compiled with LFS (large file support) by default. * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of the listed keys. * New interface gpgme_cancel() that can be used to cancel asynchronous operations. Noteworthy changes in version 0.4.4 (2004-01-12) ------------------------------------------------ * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has been renamed to "sig_class", to avoid clash with C++ compilers. In the C API, the old name "class" has been preserved for backwards compatibility, but is deprecated. |
| 2004-07-11 02:48:42 by grant beattie | Files touched by this commit (1) |
Log message: this needs -lnsl -lsocket on Solaris. |
| 2004-03-23 08:16:10 by Soren Jacobsen | Files touched by this commit (1) |
Log message: Fix build on sparc64 with gcc2. |
| 2004-03-18 10:12:18 by Johnny C. Lam | Files touched by this commit (232) |
Log message: Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES. |
New packages: