From owner-cvs-all@FreeBSD.ORG Thu Dec 23 20:45:38 2010 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 183411065672 for ; Thu, 23 Dec 2010 20:45:38 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from lab.alexdupre.com (cl-506.trn-01.it.sixxs.net [IPv6:2001:1418:100:1f9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 422458FC0C for ; Thu, 23 Dec 2010 20:45:37 +0000 (UTC) Received: (qmail 38710 invoked from network); 23 Dec 2010 20:38:55 -0000 Received: from atom.alexdupre.com (HELO ?192.168.178.12?) (sysadmin@alexdupre.com@192.168.178.12) by lab.alexdupre.com with ESMTPSA; 23 Dec 2010 20:38:55 -0000 Message-ID: <4D13B360.50204@FreeBSD.org> Date: Thu, 23 Dec 2010 21:38:56 +0100 From: Alex Dupre User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 MIME-Version: 1.0 To: Doug Barton References: <201012221916.oBMJGCMY069579@repoman.freebsd.org> <4D139A36.1080208@FreeBSD.org> <4D139DC9.1010704@FreeBSD.org> <4D13A438.70805@FreeBSD.org> <4D13AA9E.70208@FreeBSD.org> In-Reply-To: <4D13AA9E.70208@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeremy Messenger , cvs-ports@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/security/dirmngr Makefile ports/security/gnupg Makefile ports/security/gpa Makefile ports/security/gpgme Makefile ports/security/libassuan Makefile distinfo pkg-descr ports/security/opensc Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2010 20:45:38 -0000 Doug Barton ha scritto: > And what *I* am saying is that if there is a bug elsewhere, it should be > fixed elsewhere. I agree with you, but "elsewhere" is tricky here: libtool is not libassuan, but the libassuan tarball includes libtool, so you "have" to use the external libtool to handle this issue correctly. USE_AUTOTOOLS= libtool USE_GNOME= ltverhack > Meanwhile, if anyone else wants to engage in idle > speculation it's going to be ignored. Discussion based on facts is > always welcome of course. The fact is that libassuan 2.0.1 added a few interfaces, and so bumped LT_CURRENT and LT_AGE to 1 (before they were 0): # LT Version numbers, remember to change them just *before* a release. # (Code changed: REVISION++) # (Interfaces added/removed/changed: CURRENT++, REVISION=0) # (Interfaces added: AGE++) # (Interfaces removed/changed: AGE=0) # LIBASSUAN_LT_CURRENT=1 LIBASSUAN_LT_AGE=1 LIBASSUAN_LT_REVISION=0 This means that the new library is backward compatible with 2.0.0 and a shared library bump is not needed, simplifying the port update. -- Alex Dupre