head	1.2;
access;
symbols
	RELEASE_8_1_0:1.1;
locks; strict;
comment	@# @;


1.2
date	2010.08.08.20.36.39;	author dougb;	state dead;
branches;
next	1.1;

1.1
date	2010.06.14.00.42.52;	author dougb;	state Exp;
branches;
next	;


desc
@@


1.2
log
@As previously advertised, remove the old libassuan port now that all
consumers have moved to libassuan 2.0.0, or dropped the dependency
@
text
@MD5 (libassuan-1.0.5.tar.bz2) = c2db0974fcce4401f48f3fa41c4edc5a
SHA256 (libassuan-1.0.5.tar.bz2) = c58b2408d81aa6d76e9d699a2bdaafd6acc2e63e9df89a142f07aa2a4b4459f5
SIZE (libassuan-1.0.5.tar.bz2) = 297786
MD5 (libassuan-1.0.5.tar.bz2.sig) = 167c1838f56f3b85083422668b369f17
SHA256 (libassuan-1.0.5.tar.bz2.sig) = b9c47946261c264a1e162517fbf13184266e656a79b97be736d481484e9e7819
SIZE (libassuan-1.0.5.tar.bz2.sig) = 158
@


1.1
log
@Update security/libassuan to version 2.0.0, which is required by gnupg 2.0.15

Unfortunately version 2.0.0 is largely incompatible with version 1.x, so it
is necessary to have a stopgap measure while ports that depend on libassuan
can be updated. In conversation with the maintainers of the dependent ports
it was originally considered ideal to prepare updates for the ports first,
then upgrade everything to libassuan 2.x en masse. Since no action has
arisen on that front, go with plan B:

Copy security/libassuan to security/libassuan-1, and update the dependent
ports accordingly. Because this is (intended to be) a _temporary_ measure,
and because no updates for libassuan 1.x are anticipated, and because the
hope is that it can be removed sooner rather than later, it's a copy instead
of a repocopy.
@
text
@@

