[OpenAFS-devel] Re: [OpenAFS] jafs et al

[Marcus Watts]

I meant to ask about this:
Russ Allbery <rra@stanford.edu> had written:
> >> The clean approach from a Linux perspective is to have a shared library
> >> with a versioned API that you can link against.  It saves overhead,
> >> reduces memory usage, and makes packaging far cleaner.  It's just a lot
> >> more work getting it right and keeping it right.
> 
> > You've got that now.  They're called "libafsrpc.so" and
> > "libafsauthent.so".
> 
> No, I don't, because those libraries don't contain enough code to do
> everything that I care about.  There's a variety of "other stuff" that
> isn't included in those libraries.

Which "other stuff" is that?  Do you want that "other stuff" in
libafsauthent too?  Or elsewhere?

> 
> Plus, until recently (and possibly still on the release branches) the
> SONAME is broken on Linux, and no symbol versioning is happening.
> (There's a version script.  It doesn't do symbol versioning.  It does
> something else.)

What are you looking for here?  What do you expect symbol versioning
to do?  Do you expect this to affect anything beyond the text
in error messages?  Are you talking about the src/shlibafs{rpc,authent}/mapfile*
files found in the release source?

Assuming I understand what you're talking about with SONAME,
that got fixed in 1.4 between 1.4.0 & 1.4.1, and in 1.5 before 1.5.5.
SONAME doesn't have anything to do with symbol versioning,
so I might be confused about what you mean.

Also, how do you expect this to work under aix, ms windows, hpux,
and macosx?

				-Marcus Watts