Quick thing to change that i just noticed. The libtorrent-rasterbar.so version was bumped (from libtorrent-rasterbar.so.4 to libtorrent-rasterbar.so.5) and that confuses at the very least Deluge and possibly other clients as well that use the versioned library rather than the plain .so. Perhaps add a symlink in the PKGBUILD to link libtorrent-rasterbar.so.5 to libtorrent-rasterbar.so.4 or libtorrent-rasterbar.so to libtorrent-rasterbar.so.4.

Normally, i'd agree with you, but in this case, I wouldn't. First off, looking through the changelog and the commits that make up the release, there are really only API additions, not really any API breaks/removals. Second, I compiled/installed Deluge *AFTER* I compiled/installed libtorrent-rasterbar 0.14.6 and it still was looking for libtorrent-rasterbar.so.4 which makes me think lazy/stupid developer. 2009/10/8 Ray Kohler

On Thu, Oct 8, 2009 at 2:33 PM, Jeff Horelick wrote:

...

Quick thing to change that i just noticed. The libtorrent-rasterbar.so version was bumped (from libtorrent-rasterbar.so.4 to libtorrent-rasterbar.so.5) and that confuses at the very least Deluge and possibly other clients as well that use the versioned library rather than the plain .so. Perhaps add a symlink in the PKGBUILD to link libtorrent-rasterbar.so.5 to libtorrent-rasterbar.so.4 or libtorrent-rasterbar.so to libtorrent-rasterbar.so.4.

That is a bad idea. The soname version changed for a reason. You don't want to give apps expecting version 4 a version 5 library. Instead, all apps that link this library need to be rebuilt.

Jeff Horelick wrote:

Hey all,

libtorrent-rasterbar is pretty out of date (2 months and 2 package versions), so here's a PKGBUILD for the new version. I bumped the pkgver (obviously), added python to the dependency list since we *ARE* building the python bindings... Do the python packages need to be depends, or can they just be makedepends? Just curious, I don't use this myself.

T.