From owner-freebsd-ports Fri Feb 28 19:54:33 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9640137B401 for ; Fri, 28 Feb 2003 19:54:31 -0800 (PST) Received: from gate.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BF0C43FAF for ; Fri, 28 Feb 2003 19:54:31 -0800 (PST) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.13]) by gate.volant.org with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.33 #1) id 18oy4B-000IYY-00; Fri, 28 Feb 2003 19:53:40 -0800 Date: Fri, 28 Feb 2003 19:53:32 -0800 From: Pat Lashley To: Tilman Linneweh , Joe Kelsey Cc: ports@FreeBSD.org Subject: Re: WARNING: portupgrade considered harmful Message-ID: <1746690000.1046490812@mccaffrey.phoenix.volant.org> X-Mailer: Mulberry/2.2.1 (Linux/x86 Demo) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========3287483427==========" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==========3287483427========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Friday, February 28, 2003 20:57:47 +0100 Tilman Linneweh=20 wrote: > This is IMHO not a fault of portupgrade but how bsd.port.mk detects > LIB_DEPENDS. It checks if the library is in ld's path. This works as long > as this path does not contain directories with libraries not installed by > ports. If you use portupgrade to do recursive upgrades, that shouldn't matter. It should determine what is to be upgraded based on the dependancy list in the portsdb rather than relying on the recursion in the Makefiles. If you update a library, it should update everything that links to that library. This will fail if the dependancy list isn't complete or accurate. (Which usually indicates a failure of some port to indicate some library that it needs.) As to the compat/pkg issue; I've seen problems that seem to be related to having other dirs come after /usr/local/lib/compat/pkg in the search order. Run 'ldconfig -r | head' and examine the search list. If the compat/pkg dir isn't the last entry, you should re-set the list. (And let me know if you find a way to do that that's easier and cleaner than using cut-and-paste to build an ldconfig command-line with all of the directories you want...) There's also something that causes both /usr/X11R6/lib and /usr/X11R6/lib/ to be placed in the list; which makes 'portsclean --libclean' complain = about files shadowing themselves... -Pat --==========3287483427========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+YC69ncYNbLD8wuMRAgSTAKCkw53++42IO1B2Cw/KKGoA1ZrreACg1bcU iU2oNb/ZRG/J3DLXJKF37jI= =19hq -----END PGP SIGNATURE----- --==========3287483427==========-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message