From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 06:28:43 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 D662B16A4CE for ; Wed, 18 Aug 2004 06:28:43 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB92943D46 for ; Wed, 18 Aug 2004 06:28:42 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id i7I6Rukt040558; Wed, 18 Aug 2004 15:58:05 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 18 Aug 2004 15:57:56 +0930 User-Agent: KMail/1.6.2 References: <200408181222.52676.doconnor@gsoft.com.au> <200408172152.49021.kstewart@owt.com> <200408172213.04769.kstewart@owt.com> In-Reply-To: <200408172213.04769.kstewart@owt.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200408181557.56952.doconnor@gsoft.com.au> X-Spam-Score: -4.6 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_03_05,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: "Wilkinson, Alex" cc: kstewart 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:28:43 -0000 =2D----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 y= ou=20 shouldn't have to rebuild apps that use it. The most likely outcome of a broken ABI is a coredump and I don't see any o= f=20 those, all the applications I've tried work fine too. Don't forget that even if there was a static binary the X wire protocol is= =20 well defined so it wouldn't affect things. =2D --=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBIvbs5ZPcIHs/zowRAnDnAJ4jZzO6dL1Ayjrf67irfQqOKh4d3wCgi+zM a+ghRYz0ZHM7vwUKHsfFbbI=3D =3D8h9J =2D----END PGP SIGNATURE-----