Date: Sun, 12 Dec 2010 11:35:50 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Yuri <yuri@rawbw.com> Cc: freebsd-questions@freebsd.org Subject: Re: Ports: How do dependent ports upgrade when dependency shared lib version is bumped? Message-ID: <447hffuexl.fsf@lowell-desk.lan> In-Reply-To: <4D042B98.60907@rawbw.com> (yuri@rawbw.com's message of "Sat, 11 Dec 2010 17:55:36 -0800") References: <4D042B98.60907@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yuri <yuri@rawbw.com> writes: > 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? There's no way to do it fully automatically, but porters try to do this by hand, by incrementing PORTREVISION for the dependent ports. Once that is done, portupgrade will pick it up automatically. However, porters will sometimes miss subtle dependencies, especially optional ones. In this case, I don't see a direct dependency of inkscape on atkmm, so I don't know how it should have been marked. In any case, inkscape was updated shortly after atkmm, so if you upgraded everything more recently, it looks like you should have gotten inkscape rebuilt after the atkmm change.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447hffuexl.fsf>