From owner-freebsd-ports@FreeBSD.ORG Mon May 7 20:14:49 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4698316A4E2; Mon, 7 May 2007 20:14:49 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 2D57D13C43E; Mon, 7 May 2007 20:14:49 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9DB411A3C1A; Mon, 7 May 2007 13:15:29 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 783A651417; Mon, 7 May 2007 16:14:48 -0400 (EDT) Date: Mon, 7 May 2007 16:14:48 -0400 From: Kris Kennaway To: Jeremy Messenger Message-ID: <20070507201448.GA52651@xor.obsecurity.org> References: <20070502193159.GB42482@xor.obsecurity.org> <463F7236.4080108@FreeBSD.org> <20070507184231.GA50639@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: ports@freebsd.org, Doug Barton , Kris Kennaway Subject: Re: HEADS UP: xorg upgrade plans X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2007 20:14:49 -0000 On Mon, May 07, 2007 at 03:09:06PM -0500, Jeremy Messenger wrote: > >No, at a minimum I am not comfortable recommending its use until it > >saves old shared libraries across updates (I sent you email about this > >a while ago), which is a vital safety and robustness mechanism. > > I am one of people that dislike this and it is not required to get build > function. ;-) I think this option should be disable by default, because > put stuff in lib/compat/pkg hides the problems. Also: No, it is required when dealing with shared library bumps (which happen about once a week). Otherwise all of the installed ports using the library break if the new library build fails. Talk to Brooks about how annoying this is with e.g. gettext. > http://www.freebsd.org/gnome/docs/faq2.html#q2 > ============================================== > [...] > Prevent two versions of the same library. > > A common source of build failures is the existence of multiple versions of > the same library. This can happen if you have two different versions of a > port installed, or can even happen through normal portupgrade use. You can > back up the libraries in /usr/local/lib/compat/pkg and remove them, and > then run portupgrade -u -rf pkg-config. This will force a rebuild of all > GNOME-related apps (and a fair number of other apps) without retaining old > versions of libraries in /usr/local/lib/compat/pkg. > ============================================== I dispute the correctness of this entry. The old libraries in lib/compat/pkg are not linked to directly by new builds. The only situation in which something might end up being linked to 2 versions of the library is if it pulls in a library dependency from an existing port that is still linked to the old library. In this situation the build would be broken with or without lib/compat/pkg (in the latter case, you have an installed port linked to a library that is entirely missing, so that port will be nonfunctional). Kris