Date: Wed, 12 Nov 2003 03:01:58 +0100 From: Alex de Kruijff <freebsd@akruijff.dds.nl> To: Chris <racerx@makeworld.com> Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade -arR Message-ID: <20031112020158.GC3705@dds.nl> In-Reply-To: <200311111824.31778.racerx@makeworld.com> References: <20031111173315.GA30896@sillyrabbi.dyndns.org> <200311112039.21752.freebsd.nospam@mekanix.dk> <200311111824.31778.racerx@makeworld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 11, 2003 at 06:24:31PM -0600, Chris wrote: > On Tuesday 11 November 2003 01:39 pm, Bjarne Wichmann Petersen wrote: > > On Tuesday 11 November 2003 18:33, William O'Higgins wrote: > > > Quite foolishly, I ran this command without thinking it through: > > > > > > portupgrade -arR > > > > Try the -n switch (ie. portupgrade -narR), this will show which ports will > > be upgraded without doing so. > > > > The great thing about this, is once you have done this for the 1st time (as > you have) and if you continue to update your ports tree (perhaps on a nightly > basis) you can run portupgrade daily, and the time needed is sooo much > shorter. > > On a personal note - I do update my ports nightly, then run portgrade -arR > daily. I don't think it runs more then 10 mins on any day. > > Welcome to the world of maintaining your ports! Do you happen to run apache and php4? I had trouble with these two. One didn't need to be updated and the other did. The result was that apache didn't wan't to load php4. I had to fore the compilation of the other port. -- Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031112020158.GC3705>