From owner-freebsd-questions@FreeBSD.ORG Sun Dec 12 10:48:14 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id A84051065674; Sun, 12 Dec 2010 10:48:14 +0000 (UTC) Date: Sun, 12 Dec 2010 10:48:14 +0000 From: Alexander Best To: Yuri Message-ID: <20101212104814.GA52041@freebsd.org> References: <4D042B98.60907@rawbw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D042B98.60907@rawbw.com> Cc: freebsd-questions@freebsd.org Subject: Re: Ports: How do dependent ports upgrade when dependency shared lib version is bumped? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2010 10:48:14 -0000 On Sat Dec 11 10, Yuri wrote: > I recently updates the system. libatkmm-1.6.so.1 got bumped to > libatkmm-1.6.so.2, now inkscape fails: > /libexec/ld-elf.so.1: Shared object "libatkmm-1.6.so.1" not found, > required by "inkscape" > > What is the right behavior in such situation? Should all depending > packages be also automatically bumped? Or portupghrade should detect the > change and automatically upgrade dependent ports? portupgrade -rfx atkmm atkmm should take care of the issue, although portupgrade -rf atkmm is probably ok too, unless atkmm takes multiple hours to build. as a workaround you could also add an entry to /etc/libmap.conf: libatkmm-1.6.so.1 libatkmm-1.6.so.2 if things in libatkmm haven't changed too much you might get away with it for now and delay the portupgrade to some time that's more convenient to you. cheers. alex > > Yuri > -- a13x