HEADS-UP: Shared Library Versions bumped...
oberman at es.net
Mon Jul 20 18:13:36 UTC 2009
> Date: Mon, 20 Jul 2009 16:29:39 +0200
> From: Olivier SMEDTS <olivier at gid0.org>
> Sender: owner-freebsd-current at freebsd.org
> 2009/7/19 Thomas Backman <serenity at exscape.org>:
> > On Jul 19, 2009, at 20:16, Ken Smith wrote:
> >> The problem is that as of the next time you update a machine that had
> >> been running -current you are best off reinstalling all ports or other
> >> applications you have on the machine. When you reboot after doing the
> >> update to the base system everything you have installed will still work
> >> because the old shared library versions will still be there. However
> >> anything you build on the machine after its base system gets updated
> >> would be linked against the newer base system shared libraries but any
> >> libraries that are part of ports or other applications (e.g. the Xorg
> >> libraries) would have been linked against the older library versions.
> >> You really don't want to leave things that way.
> > So, to be clear: a fresh ports tree and "portupgrade -af" after building and
> > installing r195767+ should be enough to solve any problems? (installkernel,
> > installworld, reboot, portupgrade -af)
> But there won't be any problem until you do a "make delete-old-libs"
> in /usr/src/, right ?
Wrong. As soon as you start updating ports you will start getting apps
which link to both old and new versions and that does not work. If you
don't update any ports which provide shared libs, you are OK.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
More information about the freebsd-stable