From owner-freebsd-ports@FreeBSD.ORG Tue Dec 26 11:04:53 2006 Return-Path: X-Original-To: freebsd-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 DCB2316A40F for ; Tue, 26 Dec 2006 11:04:53 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9B22A13C48D for ; Tue, 26 Dec 2006 11:04:53 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GzA6t-0006Dg-8p for freebsd-ports@freebsd.org; Tue, 26 Dec 2006 12:04:44 +0100 Received: from e177218019.adsl.alicedsl.de ([85.177.218.19]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Dec 2006 12:04:43 +0100 Received: from rotkap by e177218019.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Dec 2006 12:04:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Heino Tiedemann Date: Tue, 26 Dec 2006 12:04:21 +0100 Organization: yes Lines: 26 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: e177218019.adsl.alicedsl.de User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) X-Face: v6Lci{Mw=kwHf$`7C?L-U#BHn7O\wqF-1qg#Vk%}nUQv\i^mM/.p=wU+cr)yXf#Ob+foOOxW; ir"QI!|25wG3`ywF)yh~@V.kKtr.qp+v.R; w?c@ZzM#!'/7r_+)$NjMN:]qo-]`&z~KlP}|cERO'%s9":6\ZnN/O Subject: why "-R" und not "-r"? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rotkap@gmx.de List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2006 11:04:53 -0000 Hi There, one question about this antry in UPDATING: ,---- | 20061221: | AFFECTS: users of security/gnupg | AUTHOR: kuriyama@FreeBSD.org | | The security/gnupg port was upgraded to 2.0.1 (with securty fix) | and good-old gnupg-1.4.6 was repocopied to security/gnupg1. | | Both of security/gnupg (2.x) and security/gnupg1 (1.4.x) are | designed not to conflict with each other. So you can use | security/gnupg1 for gpg(1), and use security/gnupg for gpg2(1) | commands. | | All directly dependents are $PORTREVISION bumped, so portupgrade -R | gnupg will works fine. After portupgrade, you will have both of | gnupg-2.0.1 and gnupg-1.4.6. `---- Why "portupgrade -R gnup"? Isn't it "portupgrade -r gnup"? Heino