From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 06:37:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF3E216A4CE for ; Wed, 18 Aug 2004 06:37:10 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 606FC43D1F for ; Wed, 18 Aug 2004 06:37:10 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i7I6aUNQ003435; Tue, 17 Aug 2004 23:36:37 -0700 From: kstewart To: "Daniel O'Connor" Date: Tue, 17 Aug 2004 23:36:58 -0700 User-Agent: KMail/1.6.2 References: <200408181222.52676.doconnor@gsoft.com.au> <200408172213.04769.kstewart@owt.com> <200408181557.56952.doconnor@gsoft.com.au> In-Reply-To: <200408181557.56952.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408172336.58601.kstewart@owt.com> cc: freebsd-current@freebsd.org cc: "Wilkinson, Alex" Subject: Re: Migrating to X.org with portupgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 06:37:10 -0000 On Tuesday 17 August 2004 11:27 pm, Daniel O'Connor wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 18 Aug 2004 14:43, kstewart wrote: > > One more point. When you build a new library, the only safe thing to do > > is rebuild everything that uses that library. You don't know if they > > changed an element of a structure or not. If they didn't and you rebuild > > everything, all you did is lose some cpu time. If they modified > > something, and you don't rebuild everything, then, you have introduced > > the possiblity for massive offset errors that you won't know about until > > someone breaks into your system. > > I am pretty sure that things like Xlib have quite a fixed ABI which means > you shouldn't have to rebuild apps that use it. I didn't know about that end :). > > The most likely outcome of a broken ABI is a coredump and I don't see any > of those, all the applications I've tried work fine too. Mine did to. Around that time they also made a number of changes to 3.2.3 and changed the gcc compiler. There were a number of ports that had to be rebuilt because of the upgrade in the gcc compiler. I think at some point, I just rebuilt everything. Kent > > Don't forget that even if there was a static binary the X wire protocol is > well defined so it wouldn't affect things. > > - -- -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/