(btw, why jackd doesn't read /etc/jackrc or
~/.jackrc ?)
because that means we have a config file, which means we need a
config file parser, which means we need to replicate a bunch of
code or link against another library. if jackd was a commonly
executed command for users, i could justify that. as it is, i
can't.
Seems like it would be useful for the "no jackd" case, though. (Or
you'd have to force code changes upon applications anyway.)
For Kobo Deluxe, I just hacked a simple integrated command line and
config file parser. Inherit the parser class, add your argument
there are plenty of decent config file parsers floating around.
the goal is to avoid JACK requiring other libraries, as much as
possible.
--p