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.
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".
libgcrypt was recently upgraded. So when using binary packages
it is possible for new libgcrypt (libgcrypt.so.12.1) to be installed
with old opencdk-0.5.4 package.
So bump PKGREVISION and BUILDLINK_DEPENDS (to force a new package
to be required).
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.
Changes:
* Added a compile time check for vasprintf.
* The unsigned long types were changed to unsigned int.
* Internal message digest and symmetric crypto library to simplify to
include parts of OpenCDK into an own application.
* Huge interface and naming changes to enhance the readability of the
code. Several code cleanups which means some functions are not
public any longer. No backward compatibility to force client
applications to change the interface as soon as possible.
* Simplified API for listing keys.
* Extended key node (KBNODE) API to extract attributes more easier.
* Signature sub packet API is now public.
* Read-only support for revocation keys.
* Bug fix to prevent possible DOS memory attack.
* Support for literal partial body packets.
And more...
OpenCDK (Open Crypto Development Kit) provides basic parts of the OpenPGP
message format. The aim of the library is *not* to replace any available
OpenPGP version. There will be no real support for key management (sign,
revoke, alter preferences, ...) and some other parts are only rudimentary
available. The main purpose is to handle and understand OpenPGP packets and
to use basic operations. For example to encrypt/decrypt or to sign/verify
and packet routines.
Provided by Juan RP via pkgsrc-wip with some modifications by me.
