At 2003-03-03T00:28:21Z, Kent Stewart <[EMAIL PROTECTED]> writes:

> The -rR bothers me because it is making a lot of ports that don't need to
> be updated.

It was my understand that if `-rR' would upgrade a port, then that port
needs to be upgraded.  For a non-FreeBSD perspective, look at Debian: you
are extremely discouraged from upgrading a program without upgrading all of
its dependencies, and all of their dependencies.

> I typically have 2 or 3 lines that need updating and -ruf will force
> them.

I'm allergic to the word `force'.  It's usually a synonym for "Yes, I really
want you to break it!".

I've never, ever used `-f' except when re-installing the same version of a
port (i.e. with different build options), and that may be why I've never had
the portupgrade problems that some people have.  Take this scenario:

x, y, and z are installed.  y depends on x and z.  After cvsup'ing, new
versions of all three are installed.  Furthermore, y explicitly depends on
the newest version of z to function correctly (real world examples: libpng,

Now, if you `portupgrade -rR x', it will:

1. Recompile x
2. Recurse to y
3. Realize that it has to upgrade z
4. Recompile z
5. Recompile y

so that y is correctly built with the new versions of x and z.  On the other
hand, if you `portupgrade -R x', it will:

1. Recompile x
2. Recurse to y
3. Recompile y

so that y is incorrectly built against a new version of x, but an old
version of z.

> The way I understand it, a -rR kdebase will rebuild most of XFree86 and
> etc.

True, but X doesn't update *that* often.

> The AMD 2000+ uses 6-8 hours to rebuild everything but it will rebuild all
> of kde-3.1 in 3+.

True, but you're also building KDE against old versions of required
libraries.  Why not launch a `portupgrade -ra' just before you go to bed?
Then you can wake up to a shiny, happy new system in the morning.
Kirk Strauser
In Googlis non est, ergo non est.

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to