From owner-freebsd-ports@FreeBSD.ORG Mon Dec 11 18:36:20 2006 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF0C416A47C for ; Mon, 11 Dec 2006 18:36:20 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id B593F44EAC for ; Mon, 11 Dec 2006 18:15:03 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 7382 invoked by uid 399); 11 Dec 2006 18:16:10 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Dec 2006 18:16:10 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <457DA05F.8010805@FreeBSD.org> Date: Mon, 11 Dec 2006 10:15:59 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061125) MIME-Version: 1.0 To: Jun Kuriyama References: <7mu003jdyg.wl%kuriyama@imgsrc.co.jp> In-Reply-To: <7mu003jdyg.wl%kuriyama@imgsrc.co.jp> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: Re: HEADS UP : security/gnupg will be upgraded to 2.0.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2006 18:36:20 -0000 Jun Kuriyama wrote: > Hi, > > I'm planning to upgrade security/gnupg to 2.0.1. This upgrade > includes portrevision bumps to indicate dependency changes. > > I'm testing conditional plist, upgrading procedure by portupgrade. > But I think it's almost ready to commit. > > If you have further suggestions, please let me know. Jun, Thanks for letting us know what you're plans are. I think you know what I'm going to say next. ;) As I suggested when I wrote to you in private e-mail some time ago, I think it would be more in line with the plans that the developers have for GnuPG 2.x to keep the existing gnupg port dedicated to the 1.x branch, and repo copy gnupg-devel to gnupg2. Quoting from the README for 2.x: GnuPG 2.0 is the stable version of GnuPG integrating support for OpenPGP and S/MIME. It does not conflict with an installed 1.4 OpenPGP-only version. Note that there is no binary gpg but a gpg2 so that this package won't conflict with a GnuPG 1.4 installation. gpg2 behaves just like gpg. GNUPG 1.4 AND GNUPG 2.0 ======================= GnuPG 2.0 is a newer version of GnuPG with additional support for S/MIME. It has a different design philosophy that splits functionality up into several modules. Both versions may be installed simultaneously without any conflict (gpg is called gpg2 in GnuPG 2). In fact, the gpg version from GnuPG 1.4 is able to make use of the gpg-agent as included in GnuPG 2 and allows for seamless passphrase caching. The advantage of GnuPG 1.4 is its smaller size and no dependency on other modules at run and build time. Further, in discussion on the gnupg-users list the developers have clearly stated that they will continue working on at least the 1.4.x branch of GnuPG for the foreseeable future. Therefore I think it would be more in line with the development goals for the GnuPG project, and less confusing for new users coming to FreeBSD from other platforms, to adopt the naming scheme that I proposed, although not necessarily the exact patches I sent you to implement it. If you choose not to go that direction, I would be interested in hearing your reasoning. Thanks, Doug -- This .signature sanitized for your protection