Re: libc6 dependency generation

[Brian White <bcwhite@precidia.com>]

> > What confuses me is why libc6 would make a change like that in a "minor"
> > revision (as indicated by the version number of the package).  I would
> > have expected the glibc guys to only redefine functions during the
> > change of the "medium" or "major" revision numbers.
> 
> Minor releases they only require backwards compatibility, not forwards.
> "Medium" releases are huge.  The "Major" revision is reserved for
> something which will require a global change of soname - which they
> have no intention of allowing.

And that answers my original question.  The libc6 "definition" of the
"medium" and "minor" revision numbers are different than what I had
expected them to mean.  Thank you!

Out of curiosity, would a "medium" change retain any amout of backward
compatibility?

                                          Brian
                                 ( bcwhite@precidia.com )

-------------------------------------------------------------------------------
      Sticks and stones may break bones, but words will shatter the soul.