Paul Davis schrieb:
> On Tue, May 19, 2009 at 8:33 AM, Krzysztof Foltman <wdev@email-addr-hidden> wrote:
>> A better way: allow only JACK-legacy or JACK-DBUS to be installed at the
>> same time. Situations where both jackd and jackdbus need to be used on
>> the same system are rare enough to ignore them.
>
> there is a difficulty with this otherwise very clean approach.
>
> there are other applications that want to start (and potentially) stop
> jack. if a d-bus aware version of jack is installed instead of the
> non-dbus-aware one, then applications that do not use the control API
> for this will fail. ergo: installing the dbus aware version
> (potentially) breaks the operation of control apps that predate the
> control API. not the end of the world, but not good either.
couldn't jackdbus also install a ligh wrapper jackd that translates cmd-line
args to dbus calls?
Stefan
>
> also, the current jack ecosystem is already deeply confused by the
> existence of jack1 and jack2, which have a few very subtle but
> important differences. adding yet another
> almost-the-same-but-different option is a PR disaster waiting to
> happen.
>
> --p
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev@email-addr-hidden
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Sun May 24 16:15:01 2009
This archive was generated by hypermail 2.1.8 : Sun May 24 2009 - 16:15:01 EEST