On Saturday 08 December 2007, Leo "costela" Antunes wrote:
> 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.

Good point!  Since I'm talking with them about 3 or 4 other things I 
might as well mention this.  ;)

> 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.

No hard at all.  I'm playing with it right now.

> 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

It's moot.  They're plugins in name only.  I think that one day, 
eventually, sometime in future, they plan to make these real plugins, 
but for now each is necessary for the client's function.  A while ago 
I sent them a patch that could allow 3rd parties to write their own 
output plugins--OSS, JACK, PortAudio, etc.--but upstream's priorities 
have been elsewhere.  Now that I look at it again, the patch could 
use a little more work.

Anyway,  I'll contact upstream and decide once I hear back from them.

Cheers,

John



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to