Re: Symbol versioning conventions (was Re: cvs commit: src/lib/libc/gen ...)

On Sun, Aug 26, 2007 at 12:48:41PM -0400, Daniel Eischen wrote:
> 
> Here it is on -current, feel free to redirect it to arch.
> 
> I updated my notes on symbol versioning - see "Version naming conventions"
> on downwards at:
> 
>   http://people.freebsd.org/~deischen/symver/freebsd_versioning.txt
> 
> Feel free to cut&paste anything from it in replies.

It seems that we've failed to divert the main discussion from the
cvs lists, so I'll comment on other sides of the symbol versioning
issue.

First, you wrote that a symbol having multiple versions needs to
be listed in the symbol map file under each of its versions.  I'm
afraid that the GNU ld(1) documentation doesn't suggest that.  I
believe that it is correct to list each symbol in the symbol map
only once, under its default version.

Second, we need to decide how to handle SV consistently at source
tree level.  In a trivial case, cut'n'paste or a stub function will
do, but in the more complex case of massive changes it can be hard
to reproduce the old ABI using stubs, e.g., because the new
implementation lost old bugs.  In this case, CVS history should be
preserved for the old version at file level.  A uniform approach
can be to repocopy the respective file(s) and add the version to
their name(s), e.g.: fts.c -> fts_fbsd_1_0.c.  Does it sound
reasonable?

-- 
Yar