Quote Originally Posted by probono
- what package are you trying to run
qjackctl

Quote Originally Posted by probono
- which other package you think should be included
jackit

Quote Originally Posted by probono
- how should the wrapper call the "helper binary"
jackd -v -d alsa -d hw:0 -r44100 -p512 -n2 -s -zr -H

If this runs, Apps that rely on JACK should be able to access it to transport audiostreams. Tere are some (like ARDOUR), that cannot Startwithout JACK running and many others need JACK to communicate and to sync.

To be honest: this cannot be done whithout seriously altering these binaries in the first Place,

because:

if qjackctl comes with JACK and invokes it, it is allready running, so if ARDOUR or MUSE or Rosegarden would bring their own JACK also, they need a Mechanism that stops them from starting jackd if it is already running AND a Mechanism that starts jackd, if it is not.
Not soooo big a thing to do methinks - but it needs to be done properly if klik should make these apps available.
Practically all Pro-oriented Linux-Audio-Apps need JACK, so in the future it may be a Standardcomponent for the most Distros yet until then, some wrapperscripts or even some hacks in the sources appeare unevitable to me.

Again: a very easy and usefull first step would be to inform users, that want to install the Stuff - so they could apt-get JACK and start it in a console before they start downloading klik-Packs of JACK-relying Apps.

best regards.

oh yes, to add some trouble:
the jackit-deb for the recent KANOTIX is not quite functional - at least qjackctl cannot use it.

so building it from scratch (no big thing, alsa-devel-packs are needed and fftw would be good) is recommended