John Franklin wrote:
   > We intend to bump the major version of the OS with the next release, so 
   > *if* we are going to bump the major version of libc in the near future 
   > it would make sense to do it with the major bump of the OS.  From 1.x 
   > to 2.x, people expect there might be issues, such as significant 
   > libraries being rev'd.  It may not be something we *need* to do, but if 
   > we do it now, we won't need to do it again until NetBSD 3.0.
   
   Note next major release after 2.0 would be 3.0 - we are going
   from x.y.z versioning scheme to x.y.

what's in a name? :-)
   
   > It's something we can do.  It's something we want to do.  It's 
   > something we have the opportunity to do.
   > 
   > So, let's choose to do it now.
   
   AFAICS, there's zero need to do it now.

100% agree.

   It might be necessary to
   bump the libc major on libc bind update to bind9, but not right now.

actually, hasn't this also been solved without bumping libc?  
anyway, upgrading the resolver is hardly a "good reason" to break
every existing binary....
   
   How big do you think the compat glue is ? I'd be surprised if it
   would be more than several KB - which are not even paged in if apps
   don't use it. It's really not worth the efford ATM.

"what he said."


.mrg.