Re: [LAD] [Jack-Devel] more jack/qjackctl madness

PrevNext  Index
DateMon, 18 May 2009 11:49:01 +0200
From Jan Weil <[hidden] at web dot de>
To[hidden] at jackaudio dot org
CcLinux Audio Developers <[hidden] at lists dot linuxaudio dot org>
In-Reply-Toalex stone Re: [LAD] [Jack-Devel] more jack/qjackctl madness
Follow-UpNedko Arnaudov Re: [LAD] [Jack-Devel] more jack/qjackctl madness
Follow-Updrew Roberts Re: [LAD] [Jack-Devel] more jack/qjackctl madness
On Mon, May 18, 2009 at 01:23:20PM +0400, alex stone wrote:
> Will we continue to have a Jack version minus the dbus infrastructure,
> once jack2 is released?

As an uninvolved observer I am wondering why the dbus control interface,
if it is indeed only one of many potential interfaces using the c/c++
API, is not packaged separately as an optional add-on. If it is indeed a
compile time option, the design is flawed IMHO. Generally, the new
control API sounds like a good idea but why can't the new features be
exposed as new command line tools without dbus dependency per default?
So you want the dbus interface? Fine, just install jack-control-dbus or
whatever. 

Or am I not getting it?

Jan
PrevNext  Index

1242640149.7170_0.ltw:2,a <20090518094901.GA10510 at nue018 dot nue dot tu-berlin dot de>