Hi Stephen,
On Wed, Jul 26, 2006 at 23:41:02 +0100, Stephen Wilkinson wrote:
> Looking at dependencies of Inkscape I now see that it depends on
> loudmouth which itself depends on gnutls. The newer version of
> loudmouth doesn't "link" (if that's the right term) to
> libgnutls.so.12, in fact that file isn't even part of gnutls
> (according to the file list). So it was loudmouth looking for the
> wrong library.
Libs evolve. With major changes(such as API) developers raise the version
number for libs and programs linking to them fail to find because they
are looking for a file with the old version number. Now symlinking kind
of fixes the problem sometimes but that's more gambling. If the library
calls a function with an altered API you get all kind of ugly errors.
>
> Should the installation/upgrade of Inkscape not require (and force) an
> upgrade of loudmouth and consequently gnutls to ensure that all the
> expected files are there? Or is there a loophole in the pacman system
> which means that such dependency problems can occur?
Well, sometimes there are version tied dependencies, when the packagers
know exactly that there is no compatibility with older versions. In the
given case, loudmouth wasn't update to match the new gnutls. It simply
never was seen, because not so many people watch the console and secondly
the function in Inkscape which requires loudmouth isn't used by most
people (the collaboration feature via jabber) So people just didn't run
into the problem. Moreover Inkscape and loudmouth had been updated within
a couple of days so when there was a problem it didn't existfor long.
Cheers,
tobbi
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
