Date: Wed, 06 Dec 2006 15:55:57 +0000 From: Florent Thoumie <flz@FreeBSD.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: Doug Barton <dougb@freebsd.org>, current@freebsd.org, Ladan <r.c.ladan@gmail.com>, Daniel Eischen <deischen@freebsd.org>, freebsd-current@freebsd.org, John Hay <jhay@meraka.org.za>, Rene@FreeBSD.ORG Subject: Re: HEADS UP: compat6x Message-ID: <4576E80D.8050904@FreeBSD.org> In-Reply-To: <20061206082420.8uom4bi9wggkss0w@webmail.leidinger.net> References: <456E5DAB.10608@FreeBSD.org> <4572834B.80500@FreeBSD.org> <Pine.GSO.4.64.0612030955540.14463@sea.ntplx.net> <200612051629.23067.jhb@freebsd.org> <Pine.GSO.4.64.0612051820160.26521@sea.ntplx.net> <20061206082420.8uom4bi9wggkss0w@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2EB04E2DC8209B787210F73F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Alexander Leidinger wrote: > Quoting Daniel Eischen <deischen@freebsd.org> (from Tue, 5 Dec 2006 > 18:22:41 -0500 (EST)): >=20 >> On Tue, 5 Dec 2006, John Baldwin wrote: >=20 >>> Yes, but it doesn't hurt to just bump things now. I actually agree w= ith >>> John's argument that it is beneficial to allow folks on current to >>> safely >>> use -stable apps by doing the library bump at first breakage. =20 >>> Granted, after >>> 7.0 that policy will be obsolete, but it is still relevant for >>> 7-current. :) >>> Heck, why not just enable symbol versioning in current by default now= >>> anyways? >> >> I'm waiting until after the GCC import because that should >> change the way dependencies are recorded in shared libraries, >> which really would force everyone to rebuild everything all >> over again. After the GCC import, we should bump all the >> libraries and enable symbol versioning, and hopefully you'll >> only have to rebuild things once. >=20 > We have several upcomming stuff which ideally should be coordinated > here. The symbol versioning (and the corresponding bump of the version > of some libs) results in the need to rebuild everything, and the import= > of X.org 7.x would result in the need to rebuild some ports (when an > user wants to update). I don't know if the import of gcc4 will need a > rebuild of everything too. While it might be a good idea to rebuild every X application after X.org 7.2 is merged, I don't think it's mandatory. > Could all involved people please speak with each other (or tell us you > did already) and try to coordinate a little bit? If everything is alright, X.org 7.2 should hit the tree by Christmas. Don't know if you need more information. Cheers. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --------------enig2EB04E2DC8209B787210F73F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFdugSMxEkbVFH3PQRCs34AJwMmEjrARAIij8maAbqAP0HWexFPgCfXE3g icbTPsg+nmbanyhVaivtzwc= =Z4AQ -----END PGP SIGNATURE----- --------------enig2EB04E2DC8209B787210F73F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4576E80D.8050904>