On Sunday 02 March 2003 03:24 pm, Kirk Strauser wrote:
> At 2003-03-02T22:15:59Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> > portupgrade -puf portupgrade
> > portupgrade -pufr png
> > portupgrade -pufr fontconfig
> > portupgrade -pufr libxml2
> > portupgrade -pufr ghostscript-gnu
> Interesting. I almost always user `portupgrade -rR foo' without
> other options. That way, recursion works in both directions, and
> every package that could possibly be affected in any way by upgrading
> `foo' gets updated. I've been doing this for months and have never
> encountered a problem situation. Has anyone upgraded this way and
> still had trouble?
The -rR bothers me because it is making a lot of ports that don't need
to be updated. I typically have 2 or 3 lines that need updating and
-ruf will force them. If I have more than 2 intersections, I do a -ufa.
With the -f, you see the messages about x is need by y-z but I will
delete it anyway. The way I understand it, a -rR kdebase will rebuild
most of XFree86 and etc.
The AMD 2000+ uses 6-8 hours to rebuild everything but it will rebuild
all of kde-3.1 in 3+. I also create packages on the 2000 for upgrades
on my slower machines and ftp the packages to the slower systems. The
only difference is that I then use -Pufr instead of -pufr.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message