18 Apr
2010
18 Apr
'10
3:42 p.m.
On Sunday 18 April 2010 00:14:31 Philipp wrote:
Excerpts from Arnold Krille's message of
2010-04-17 23:15:11 +0200:
Because libjack (the same as libpulse) will start jackd if its not running.
Unless that server-package is not installed:-) That is why these two should be
separate. Sometimes you really don't want to run jack. But the
developers/packagers of that music-player don't have a separate plugin and
package for the jack-output. So you need the jack-lib to install the player.
But you don't need the jack server to run that music player...
...
That way your favourite
music player can have an output plugin that looks for jack and if that is
not running, looks for pulse and finally choose direct alsa for
playback...
I don't see why jack needs to be splitted for this, it works just
fine
with jack installed in a single package. Example Audioplayer: Aqualung In general it seems to be a matter of taste, and while
debian folk sees
benefits in it others simply don't think it's worth the trouble.
Hm, which distribution apart from gentoo do you know that has jacks libs and
server/apps in one package?
IMHO it simply shouldn't get in the way.
Thats exactly the not-so-simple point: Some developers make it very hard for
users and packagers...
Have fun,
Arnold