Date: Wed, 18 Aug 2004 15:57:56 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-current@freebsd.org Cc: kstewart <kstewart@owt.com> Subject: Re: Migrating to X.org with portupgrade Message-ID: <200408181557.56952.doconnor@gsoft.com.au> In-Reply-To: <200408172213.04769.kstewart@owt.com> References: <200408181222.52676.doconnor@gsoft.com.au> <200408172152.49021.kstewart@owt.com> <200408172213.04769.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408181557.56952.doconnor>