From owner-freebsd-ports@FreeBSD.ORG Mon Nov 13 19:02:19 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0721B16A417 for ; Mon, 13 Nov 2006 19:02:19 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 806B743D66 for ; Mon, 13 Nov 2006 19:01:53 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Mon, 13 Nov 2006 14:01:45 -0500 id 000564D5.4558C119.000122D9 Received: from Internal Mail-Server by mx01 (envelope-from wmoran@collaborativefusion.com) with AES256-SHA encrypted SMTP; 13 Nov 2006 14:01:44 -0500 Date: Mon, 13 Nov 2006 14:01:43 -0500 From: Bill Moran To: Harlan Stenn Message-Id: <20061113140143.11976c73.wmoran@collaborativefusion.com> In-Reply-To: <20061113182501.EE51B2841A@gwc.pfcs.com> References: <20061113173025.E8A672841A@gwc.pfcs.com> <20061113125057.f8334988.wmoran@collaborativefusion.com> <20061113182501.EE51B2841A@gwc.pfcs.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.10.6; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: portupgrade, apache2/apache22, php4/php5 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, 13 Nov 2006 19:02:19 -0000 In response to Harlan Stenn : > Thanks Bill, > > > Using portupgrade's -o option, you can replace on port with another. > > For example: > > portupgrade -o www/apache22 apache > > > > Will replace whatever version of apache you've got installed with > > Apache-2.2, including rearranging any required dependencies so they > > point to the new port. Usually, when I have problems with portupgrade > > like you describe, it's because some already installed port requires > > something I don't want as a dependency. The above trick has fixed it > > every time for me. > > Will this "keep" across a "make update", or do I need to re-do it every > time I update /usr/ports? I'm not familiar with using "make update" and I don't see any info on it in man ports. However, the procedure I described will manipulate your package database. It does not change anything in the ports tree itself. As a result, tools (such a portupgrade) that use the package database to determine dependencies will continue to use that data. It is possible that future, drastic reorganizations to the ports tree could force you to do additional manual corrections, but it's been my experience that you'll have that now and again no matter what you do. -- Bill Moran Collaborative Fusion Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.