Date: Tue, 14 Nov 2006 09:42:47 -0500 From: Vivek Khera <vivek@khera.org> To: ports@freebsd.org Subject: Re: portupgrade, apache2/apache22, php4/php5 Message-ID: <695E1210-3318-4B0D-913C-C67D641AD8A9@khera.org> In-Reply-To: <20061113172509.eba487b1.wmoran@collaborativefusion.com> References: <20061113173025.E8A672841A@gwc.pfcs.com> <20061113125057.f8334988.wmoran@collaborativefusion.com> <20061113182501.EE51B2841A@gwc.pfcs.com> <20061113140143.11976c73.wmoran@collaborativefusion.com> <20061113221853.4C78D2841A@gwc.pfcs.com> <20061113172509.eba487b1.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-8-524573711 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Nov 13, 2006, at 5:25 PM, Bill Moran wrote: > In response to Harlan Stenn <Harlan.Stenn@pfcs.com>: >> >>>> 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. >> >> I run "make update" from /usr/src - it updates /usr/src, /usr/ >> ports, etc. > > portupgrade updates the information in /var/db/pkg. If make update > doesn't change /var/db/pkg, then the two will not affect one another, > for better or for worse. What "make update" does is run cvsup for you based on your settings in /etc/make.conf of which SUPFILES to use for updating your system. It has not much to do with portupgrade other than updating the ports tree. --Apple-Mail-8-524573711--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?695E1210-3318-4B0D-913C-C67D641AD8A9>