library clash: system vs. ports. What to do?

[Brandon S. Allbery KF8NH]

On Sun, 2004-09-19 at 20:56, Rob wrote:
> ** /usr/local/lib/libcrypto.so.3 is shadowed by /usr/lib/libcrypto.so.3
>          /usr/lib/libcrypto.so.3 <- ?
>          /usr/local/lib/libcrypto.so.3   <- openssl-0.9.7d_1

You got that because you installed/upgraded ports depending on the
openssl libraries during the period when the base system's openssl
libraries were an older insecure version so the ports system installed
the one from ports instead.

You can just stay with ports and not have problems unless you use mpd,
which as of my last cvsup set a BROKEN="doesn't build against ports
openssl" if you had ports openssl installed.  I ended up extracting a
list of dependent ports with "pkg_info -r openssl\*", "pkg_deinstall -f
openssl", then "portupgrade -f" the ports listed by the first command.

(However I'm still seeing this with libreadline; haven't yet gone in to
see what screwy dependency brought it in or whether I can go back to the
system one, or if maybe someone thinks this kind of thing is a *good*
idea for some reason.  Feh.)

-- 
brandon s. allbery    [linux,solaris,freebsd,perl]     allbery at kf8nh.com
system administrator      [WAY too many hats]        allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon univ.         KF8NH