From owner-freebsd-questions Sun Mar 2 17:25:25 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B20C37B401 for ; Sun, 2 Mar 2003 17:25:22 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DDF143F3F for ; Sun, 2 Mar 2003 17:25:21 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (kirk@pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.7/8.12.7) with ESMTP id h231PJxc088657 for ; Sun, 2 Mar 2003 19:25:19 -0600 (CST) (envelope-from kirk@strauser.com) To: freebsd-questions@freebsd.org Subject: Re: Portupgrade -- revisited From: Kirk Strauser Date: Sun, 02 Mar 2003 19:25:19 -0600 In-Reply-To: <200303021628.21627.kstewart@owt.com> (Kent Stewart's message of "Sun, 2 Mar 2003 16:28:21 -0800") Message-ID: <87healw8ao.fsf@strauser.com> Lines: 58 X-Mailer: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 References: <20030302192233.GA326@willow.raggedclown.intra> <200303021415.59947.kstewart@owt.com> <87r89pwdwa.fsf@strauser.com> <200303021628.21627.kstewart@owt.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Content-Transfer-Encoding: quoted-printable At 2003-03-03T00:28:21Z, Kent Stewart 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, gd). 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. =2D-=20 Kirk Strauser In Googlis non est, ergo non est. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+Yq7/5sRg+Y0CpvERAsoCAKCT2GCiqbdmq6lipZnz2lKFZHKxfQCdHgL0 P2DRc4dqbJe5sQuDE9S1gm4= =JVMA -----END PGP SIGNATURE----- --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message