From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 10:51:45 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 976CB106564A for ; Thu, 1 Sep 2011 10:51:45 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s10.blu0.hotmail.com (blu0-omc3-s10.blu0.hotmail.com [65.55.116.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4C0338FC16 for ; Thu, 1 Sep 2011 10:51:45 +0000 (UTC) Received: from BLU0-SMTP176 ([65.55.116.73]) by blu0-omc3-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 1 Sep 2011 03:51:44 -0700 X-Originating-IP: [76.182.105.57] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([76.182.105.57]) by BLU0-SMTP176.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 1 Sep 2011 03:51:43 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RqL4G0mgdz2CG4t for ; Thu, 1 Sep 2011 06:51:42 -0400 (EDT) Date: Thu, 1 Sep 2011 06:51:41 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20110901034552.GB2633@reemsky> References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> <20110901034552.GB2633@reemsky> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 01 Sep 2011 10:51:43.0451 (UTC) FILETIME=[230F1AB0:01CC6895] Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 10:51:45 -0000 On Wed, 31 Aug 2011 20:45:54 -0700 Roman Bogorodskiy articulated: > Kurt Jaeger wrote: > > > > GnuTLS has been updated. URL: > > > > > > > > > I was wondering if there is any work being done on getting the new > > > version into the ports tree. GnuTLS 3.0.x branch replaces the > > > GnuTLS 2.12.x branch as the supported stable branch. The > > > experimental 2.99.x branch is now probably comatose as well. > > > > gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why > > we're still at 2.x ? > > > > And re-testing the whole dependencies on that -- sounds like a > > close call for 9.0-REL... > > Hello, > > p11-kit is not a main issue indeed. > > First of all, I'd prefer to wait some time and see what kind of > problems gnutls users have with the new branch since it's quite new > still, the first 3.0 release was just about one months ago. > > And yes, it takes some time to build-test all the dependencies and > additionally it's nice to be able to run-test all the stuff (which I > obviously cannot do), so I just test a number of more or less popular > ports in runtime, but it almost always happens that some of the ports > end up broken after update. > > So I would prefer to wait with the update a couple of weeks. Or, if > there's an urgent need I may consider adding it as gnutls3 meanwhile. IMHO, renaming the existing port to gnutls2 would leave the "gnutls" port name available for the new 3.x version. Personally, I think it would eliminate a lot of confusion. I know on the "claws-mail" forum, there has been chatter from the developers about work they did to insure that the app works with the 3.x version and still be compatible with the older 2.x version. Other than that, I have no actual knowledge of how other programs will interact with it. In any case, releasing this into the ports system with the advanced notice that its compatibility with existing ports is still undetermined as well as expressly requesting feedback on ports that break or otherwise fail with this new version would be advisable and welcome. Way too many ports are being released lately with no advanced warning that they were not tested properly. Just my 2¢. -- Carmel ✌ carmel_ny@hotmail.com