2008/8/5, Daniel Stenberg wrote:

> > How do 'people' handle having several versions, with different ABI, of the
> same library installed on a system so that the user can choose at will which
> one to use ?
> >
>
> I don't know of any systems that keep them around to let the user pick. The
> older ones are just left at times to let already built programs remain
> functional, but newly built programs (typically) just use the latest and
> greatest.
>
> > And if each version, additionally, has incompatible public header files ?
> >
>
> Following the above logic, the installed headers are then only for the
> latest version that new programs use. The ones that are compiled now.

Ok! I interpret that as, that at most there is one development library
version installed in default locations which include header files and
binaries. While for backwards compatibility(functionality reasons
there might also coexist previous versions of the binary shared
library installed in default location but without its header files.

Most of the time the simplest answer is the right one. I had lost a
bit of perspective and was thinking about impossible scenarios. ;-)

-- 
-=[Yang]=-