Is there any reason not to change the soname, if it's that incompatible? it's going to be *hard* to upgrade if we have to basically redo the last month worth of bootstrapping from scratch. If we can use a new soname, I can deal with moving forward with this release... but if we can't do that, or the equivalent, I'd have to recommand *not* using this libc release until it does change enough (and stabilize) that an soname change gets made.
-- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
