RE: libpam and symbol versioning

>the next release of Linux-PAM will have symbol versioning enabled.
>While this is not a problem at runtime for old binaries, lsblibchk
>does complain that it cannot find the functions without symbol
>versioning.
>
>What can we do here?

That's going to take some redesign, and I don't really see
how we can figure this out.  lsblibchk thinks a symbol is
either versioned, or unversioned, and doesn't know how to
mix them.  It wouldn't be too hard to say "found versioned
symbol when expecting unversioned - okay", but that seems to 
open the door to not catching real changes. For example,
this would make both foo@VER_1.0 and foo@ver_1.1 acceptable,
which is pretty clearly the wrong thing.

Open to clever suggestions, of course.