Date: Thu, 9 Oct 2003 01:07:25 +0100 From: Jez Hancock <jez.hancock@munk.nu> To: freebsd-questions@freebsd.org Subject: Re: cvsup and portupgrade Message-ID: <20031009000725.GA21291@users.munk.nu> In-Reply-To: <20031008113325.B11482@asu.edu> References: <20031008113325.B11482@asu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 08, 2003 at 11:33:25AM -0700, David Bear wrote: > > I'm still trying to muddle through the loads of different ways to keep In addition to the other good advice given in this thread - when you get used to portupgrade remember to edit /usr/local/etc/pkgtools.conf. This file allows you to specify how portupgrade behaves when upgrading ports matching a pattern, say like 'www/mod_php4'. For example if you use mod_php4 and opt to run portupgrade on that port once a week, generally you will be told that the port is 'out of date', since the mod_php4 is updated generally once every few days. However if you allow portupgrade to just upgrade mod_php4 as it sees fit, it will not by default rebuild the port with all the options you chose originally. To get around this you can include options in /usr/local/etc/pkgtools.conf to specify which features you want mod_php4 to be built with when modified using portupgrade or portinstall, saving the hassle of having to 'make clean deinstall' and then 'make install' again, selecting all the options you want manually. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031009000725.GA21291>