On Tue, 20 Sep 2005, Scott Long wrote: > Daniel Eischen wrote: > > > > Sure, symbol versioning would be great to have, but I still don't > > know why library versions are bumped when they don't need to be. > > It's like we've thrown up our hands and said "Something has changed > > in one or more of the libraries, and we don't know how this affects > > other libraries, so we're going to bump them all." Speaking for > > the thread libraries, they were not users of any of the changed > > ABIs -- there was no reason to bump them. > > > > We have a very strong history of making changes in our base libraries > that have very unintended consequences. And as far as I can recall, we have ironed them all out in -current before any release. > Try running the Java binaries > for 4.x, the only ones that we are certified to distribute, on 5.x or > 6.x. Why? Do they not work with the compat libraries installed? > I put this problem forward a year ago and asked for help on solving it. > It's not like I woke up one morning and decided to screw around with > the libraries for the hell of it. I don't think anyone thinks that. But I prefer the old way. If we're not properly keeping track of our ABI changes and what they affect, then let's work on that problem. Symbol versioning isn't going to solve that for us anyways. -- DEReceived on Tue Sep 20 2005 - 16:55:52 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:43 UTC