From owner-freebsd-current@FreeBSD.ORG Fri Jun 18 18:20:07 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 986B8106567A for ; Fri, 18 Jun 2010 18:20:07 +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 C70E38FC1B for ; Fri, 18 Jun 2010 18:20:06 +0000 (UTC) Received: (qmail 87401 invoked from network); 18 Jun 2010 18:20:04 -0000 Received: from atom.alexdupre.com (HELO ?192.168.178.12?) (sysadmin@alexdupre.com@192.168.178.12) by lab.alexdupre.com with ESMTPSA; 18 Jun 2010 18:20:04 -0000 Message-ID: <4C1BB8D7.4030909@FreeBSD.org> Date: Fri, 18 Jun 2010 20:20:07 +0200 From: Alex Dupre User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.1.9) Gecko/20100317 SeaMonkey/2.0.4 MIME-Version: 1.0 To: Kevin Oberman References: <20100618180302.99F5D1CC0D@ptavv.es.net> In-Reply-To: <20100618180302.99F5D1CC0D@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Doug Barton , current Subject: Re: Having a problem with security/libassuan-1 when compiling gnupg. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 18:20:07 -0000 Kevin Oberman ha scritto: >> 5. opensc ale@ has indicated that he would prefer to wait to update his >> port until a new version that supports assuan 2.0.0 is released. Update: the signer plugin (that requires libassuan) will be removed in opensc 0.12 release. > OK. I see dirmgr and gnupg are now ready for libausaan V2.0.0, but I > also have opensc installed and MUST have it working. If I upgrade to > libassuan-2.0.0, will that break opensc? I assume, since it was not a > shared library, that this will not be a problem, but I wanted to be > sure. You are safe. -- Alex Dupre