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

[Derrick J Brashear]

On Fri, 16 Mar 2007, Marcus Watts wrote:

>> 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.)

Symbol versioning is wretched anyway. Like so much else, it may be there 
is nothing better in its space, though the value of being in that space is 
unclear.

> 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?

That's just which symbols get exported.

> 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?

"Badly"