John Stamp wrote: > The library isn't very useful for other applications; it's for lastfm > and its bundled plugins: /usr/lib/lastfm/services/*. Also, upstream > kept the same SONAME version for 1.4.0, but it's incompatible. So > no, I wouldn't call that stable.
Just to be extra polite I'd ask upstream if they want people to be able to use this lib. Perhaps they haven't really thought about it! :-) This could be enough nudging to make them either bump the SONAME for the next release or include it with the other libs in the lastfm subdir. > Of course, lintian will complain if I remove the SONAME > E: sharedobject-in-library-directory-not-actually-a-shlib > So perhaps it would be best to use RPATH and make it a private library > in /usr/lib/lastfm. Regardless of what upstream says, it shouldn't be too hard (but I haven't looked at the code) to patch the build system to move the lib to /usr/lib/lastfm. Since the executable already has RPATH set for the other libraries that are there, only moving it should be enough to clear things up. OTOH, if upstream decides to stabilize this lib (perhaps opening up way for people to contribute some third-party plugins), splitting the package should also be fairly easy. As a last idea: depending on which plugins (built-in or otherwise) are available, it could be worthwhile to split the package even if the lib is unstable, since then you could also split the plugins into separate packages to reduce the dependencies on people with specific needs. But if it only has some 2 or 3 basic built-in plugins which are all needed, this point is moot (but so is the point in having "plugins"! :-) ). Cheers -- Leo "costela" Antunes [insert a witty retort here]
signature.asc
Description: OpenPGP digital signature
