From owner-freebsd-ports@FreeBSD.ORG Mon Nov 13 18:35:11 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 B19E916A52D for ; Mon, 13 Nov 2006 18:35:11 +0000 (UTC) (envelope-from Harlan.Stenn@pfcs.com) Received: from gwc.pfcs.com (gwc.pfcs.com [70.88.151.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 559084403B for ; Mon, 13 Nov 2006 18:25:08 +0000 (GMT) (envelope-from Harlan.Stenn@pfcs.com) Received: from spike.pfcs.com (localhost.pfcs.com [127.0.0.1]) by gwc.pfcs.com (Postfix) with ESMTP id EE51B2841A; Mon, 13 Nov 2006 13:25:01 -0500 (EST) To: Bill Moran In-reply-to: <20061113125057.f8334988.wmoran@collaborativefusion.com> References: <20061113173025.E8A672841A@gwc.pfcs.com> <20061113125057.f8334988.wmoran@collaborativefusion.com> Comments: In-reply-to Bill Moran message dated "Mon, 13 Nov 2006 12:50:57 -0500." X-Mailer: MH-E 7.4.2; nmh 1.2; XEmacs 21.4 (patch 19) Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Mon, 13 Nov 2006 13:25:01 -0500 From: Harlan Stenn Message-Id: <20061113182501.EE51B2841A@gwc.pfcs.com> Cc: ports@freebsd.org, Harlan Stenn 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 18:35:11 -0000 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? H