Re: What's going on with "testing"?
On Fri, May 23, 2003 at 04:51:59PM -0500, Doug MacFarlane wrote:
> On Fri, 2003-05-23 at 14:21, stan wrote:
> > Lets say I have package a that debidns on lib b, at rev 1.0. now somebody
> > else, asy package c needs lib b a 2/0. so they package lib b at that level,
> > and put it in testing. Now I update my machine. Let's say I have package a
> > and c on my machine. Why cnat's the package managment software simply get
> > package c and the new lib b, install them, and leave the 1.0 version of lib
> > for package a?
> >
> > Shared libraries do carry version numbers you know.
> >
> > What am I missing?
>
> My programming days are far behind me, so I may be mistaken, but I
> believe that while shared libraries carry version numbers, they are
> called by just their names. You may have lib_b_1.0 and lib_b_2.0 on
> your system, but lib_b will be symlinked to one or the other.
This is not quite true. Applications are generally linked to
libb.major-number (so not the full version number, but the "major
number" which carries connotations of compatibility). You can see what's
going on using ldd.
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: