Log message:
Recursive revision bump / recommended bump for gettext ABI change.

Log message:
Update to 0.9.13. This is a bug fix release.

Log message:
Update from 0.9.10 to 0.9.11. This is part of a multi-package update
for S/MIME capability involving gnupg-devel and dirmngr also. The
changes to this pkg are bug fixes.

Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.

Log message:
Add RMD160 digests.

Log message:
Update to release 0.9.10. This is a bugfix release.

Log message:
1) Taking over maintainance of package on agreement with previous
   maintainer Klaus Klein.
2) Update to version 0.9.7 to satisfy version requirements for, soon to
   be committed, gnupg2 (1.9.10) that provides SMIME support.
Libksba is a library to make the tasks of working with X.509 certificates,
CMS data and related objects more easy. It a highlevel interface to the
implemented protocols and presents the data in a consistent way.

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.

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".

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.