Re: obsoleting shlibs - what's the plan

[der Mouse <mouse%Rodents.Montreal.QC.CA@localhost>]

>> Seems to me that each of these is a bug that should be fixed (one,
>> that the dynamic linker is willing to load the same library in
>> multiple major versions; two, [...]).
> ELF doesn't know about major versions; it only knows about sonames,
> which are strings.  It is only by convention that these strings end
> in what we are pleased to call a major version number.

Has anyone, anywhere, seen an ELF library whose name ends with digits
but for which those digits do not have the semantics of a major version
number?  (I'm thinking that perhaps our dynamic linker should know
about major version numbers even if the ELF spec proper does not.)

> It's also not clear that loading two instances of the "same" library
> is necessary wrong in all cases.

Okay, but I think it should take specific non-default configuration to
achieve this.  Renaming one or both libraries, maybe, or setting
IGNORE_SHARED_OBJECT_MAJOR_VERSION_CONFLICTS=YES in the environment, or
something.

/~\ The ASCII                           der Mouse
\ / Ribbon Campaign
 X  Against HTML               mouse%rodents.montreal.qc.ca@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B