cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h

Daniel Eischen deischen at
Mon Aug 27 18:31:01 PDT 2007

On Tue, 28 Aug 2007, Yar Tikhiy wrote:
> Example: Assume we released 7.0-R with all symbols at FBSD_1.0.
> Before the 8.0 release cycle starts, struct FTS and struct FILE
> change, perhaps a few times each, thus affecting the fts(3) and
> stdio(3) global symbols.  At the very first change to a symbol or
> their group, its 7.0-R variant is preserved at FBSD_1.0 and its
> default version becomes FBSD_1.1.  Later changes to the current
> variant of that symbol don't affect its version.  Consequently,
> 8.0-R is released with the new fts(3) and stdio(3) symbols at
> FBSD_1.1, their 7.0-R variants at FBSD_1.0, and the rest of symbols
> still at FBSD_1.0 because they are unchanged.  Let's note that
> CURRENT users had to rebuild ports depending on fts(3) or stdio(3)
> _each time_ an ABI component changed.

I think you're a little confused here.  CURRENT users did NOT have
to rebuild ports when fts(3) or stdio(3) ABIs changed.  They
would only have to rebuild if one of these ABIs changed _more
than once between releases_.  That hasn't ever happened to my
knowledge in the past, and it really shouldn't happen as long
as things are tested and reviewed properly.


More information about the cvs-src mailing list