In message <[EMAIL PROTECTED]> Peter Wemm writes:
: Personally, I think we place far too much weight on the major number thing.
: I think we should be allowed to bump it when the alternative is 'major pain'
: to developers.
The more I think about this, the more that I think that you are right.
I'd go farther and also say that we won't produce a
libcompat/libc.so.5.uu or any other "current only" libc versions.
: I also object to hacking around like this. I would far prefer that we fix
: it properly. We *need* to be able to innovate, especially with locking in
: libc in 5.x. I suspect we will have major events like this several more
: times before 5.0-R when we add in hooks for KSE or rfork threading.
And that's the argument that tipped me over from hacking around it...
That looks good. I especially like the coupling of the std* changes
to the new major version. I've killed my other build and will try to
build this one.
: Lets commit that and get on with life. Existing binaries will just keep
: on running.
: And if we dont ship libc.so.5, in 5.0-R, then *so what*?
I'd like to see a bias against major bumps remain in place, but I
think that this change requires one. That is, we still don't
generally bump major verions, but are allowed to when the pain is
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message