From owner-freebsd-ports@FreeBSD.ORG Mon Dec 5 18:16:24 2005 Return-Path: X-Original-To: freebsd-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 E310716A420 for ; Mon, 5 Dec 2005 18:16:24 +0000 (GMT) (envelope-from hemi@puresimplicity.net) Received: from just.puresimplicity.net (just.puresimplicity.net [68.77.126.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA55D43D4C for ; Mon, 5 Dec 2005 18:16:23 +0000 (GMT) (envelope-from hemi@puresimplicity.net) Received: from just.puresimplicity.net (localhost.puresimplicity.net [127.0.0.1]) by just.puresimplicity.net (8.13.4/8.13.4) with ESMTP id jB5IGMl2062834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Dec 2005 12:16:22 -0600 (CST) (envelope-from hemi@just.puresimplicity.net) Received: (from hemi@localhost) by just.puresimplicity.net (8.13.4/8.13.4/Submit) id jB5IGMKM062833; Mon, 5 Dec 2005 12:16:22 -0600 (CST) (envelope-from hemi) Date: Mon, 5 Dec 2005 12:16:22 -0600 From: Josh Tolbert To: "Michael C. Shultz" Message-ID: <20051205181622.GA62695@just.puresimplicity.net> References: <007b01c5f9c0$5efb1f00$75d65d42@bakuhatsu.net> <200512050934.56743.ringworm01@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512050934.56743.ringworm01@gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-ports@freebsd.org Subject: Re: Updating Apache 2.0.55 to 2.2.0 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, 05 Dec 2005 18:16:25 -0000 On Mon, Dec 05, 2005 at 09:34:56AM -0800, Michael C. Shultz wrote: > On Monday 05 December 2005 09:21, Matt Sealey wrote: > > I want to move our server to Apache 2.2.0 that was just released and is now > > in the ports tree. I am concerned that > > > > 1) I have to uninstall Apache 2.0.55 to let the new one install properly > > 2) it might not build okay and our webserver will be dead while I fix it > > > > What exactly is the recommended way to move from apache20 to apache22 in > > the ports tree, with minimal fuss or downtime? Could I just install with > > FORCE_PKG_REGISTER=1 and so on, and then remove apache20 from the ports > > database as a hack? Is that safe? > > portmanager (sysutils/portmanager) will handle this for you smoothly, > > first backup your original apache like this: > > cd /usr/ports/packages/All && pkg_create -b apache-2.0.55 > > make sure you have a apache-2.0.55.tgz afterwards > > then run > > portmanager -u -l > > portmanager will remove the old apache and install the new one. > > If the new version doesn't work for some reason just pkg_delete it and > pkg_addthe one you backed up: > > pkg_add /usr/ports/packages/All/apache-2.0.55.tgz > > -Mike portupgrade has never failed me. One of portupgrade's best-kept secrets (for those that don't read the man page, anyway) is the -o flag. It's generally as easy as 'portupgrade -o www/apache2 www/apache22'. Of course, you might want to see if you need any flags in the apache22 Makefile and season portupgrad to taste with -m. Thanks, Josh -- Josh Tolbert hemi@puresimplicity.net || http://www.puresimplicity.net/~hemi/ If your sysadmin's not being fascist, you're paying him too much. --Sam Greenfield