From owner-freebsd-ports@FreeBSD.ORG Tue Dec 12 09:14:23 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 3D22316A403 for ; Tue, 12 Dec 2006 09:14:23 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail30.syd.optusnet.com.au (mail30.syd.optusnet.com.au [211.29.133.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD44D43CAF for ; Tue, 12 Dec 2006 09:13:00 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c58-107-94-118.belrs4.nsw.optusnet.com.au [58.107.94.118]) by mail30.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id kBC9E1Q9013373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Dec 2006 20:14:20 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id kBC93XGu001541; Tue, 12 Dec 2006 20:03:33 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id kBC93Xk6001540; Tue, 12 Dec 2006 20:03:33 +1100 (EST) (envelope-from peter) Date: Tue, 12 Dec 2006 20:03:33 +1100 From: Peter Jeremy To: Jun Kuriyama Message-ID: <20061212090333.GA833@turion.vk2pj.dyndns.org> References: <7mu003jdyg.wl%kuriyama@imgsrc.co.jp> <457DA05F.8010805@FreeBSD.org> <7mr6v6ht57.wl%kuriyama@imgsrc.co.jp> <457E5DB4.7030204@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <457E5DB4.7030204@FreeBSD.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) 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: Tue, 12 Dec 2006 09:14:23 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Dec-11 23:43:48 -0800, Doug Barton wrote: >If this is your plan, it leads me to the next question, which is how >are you going to handle the fact that GnuPG 2.x does not install a >binary named "gpg?" As an end user, I see this as a real issue. If I upgrade a port, I expect the upgraded port to have a similar user interface. From the comments in this thread, it seems that there are significant changes between gnupg 1.x and gnupg 2.x. >to suggest to users that 2.x is the default, I think we need to >provide support for those legacy(?) apps that think gnupg is spelled gpg. Keep in mind that for a significant number of people, gpg is effectively embedded in their MUA or other tools so a UI change is a real PITA. In my case, about the only time I actually use gpg directly is when I need to edit a key. The rest of the time, I rely on a pile of commands embedded in my .muttrc I would prefer to see gnupg 2.x introduced as security/gnupg2 --=20 Peter Jeremy --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFfnBl/opHv/APuIcRAiqmAJ9/7788XY7LGFtvJbKGij+v10MwSgCePB+z FTQKYFNDLMcaJSUhE4t3SNY= =Fvkp -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE--