21 Sep
2018
21 Sep
'18
1:27 p.m.
On Fri, 21 Sep 2018 07:39:01 +0000 Rui wrote:
you may be misunderstanding my suggestion or my position in this - i am
not the debian maintainer - i have no control over the user skel and it
would be intrusive and pretentious to write to their .bashrc - i am the
upstream maintainer trying to satisfy both debian who wants clients to
autostart JACK, and also non-debian users who may take my binary
packages or compile themselves
i was suggesting to add a switch to the ./configure script of
freewheeling (not to JACK) such as: '--enable-jack-autostart', that
would select between two '#ifdef' blocks in the source code at
compile-time; one with 'JackNoStartServer' passed to jack_client_open()
and the other with 'JackNullOption' depending on whether or not
'--enable-jack-autostart' was given to ./configure - debian could use
that switch, debian users could over-ride that behavior with
JACK_NO_START_SERVER if they choose to, and others could choose for
themselves at compile-time; all without anyone patching
i think what i
should do is have it 'JackNoStartServer' by default, and
add a configure option to enable it
i'm afraid it's too late for that going into the decade old stable
jack-API;
better resort to set JACK_NO_START_SERVER=1 on default users shell
profile.