Re: [Jack-Devel] ladish + jack autoconnect

On Sun, Jan 08, 2012 at 01:01:06AM +0100, Adrian Knoth wrote:

> ...
> It's exactly what we're facing here. We could probably continue to argue
> purity vs. pragmatism for weeks.

It's not a matter of 'purity'. What you call 'purity' is just an
other form a pragmatism - one that takes a longer term and pro-
active view rather than a short-term and merely reactive one.

> How about the following: let's do both - work around the bug to please
> the user *AND* blame the application developers.

Application developers will just bypass the autoconnect restriction
which is trivially easy. Just call system ("jack_connect ....") or
create a second Jack client within the app to do the connections.

This sort of hack is not a real solution to what _may_ be real
problem (and I'm not even convinced of the latter). And if any
app can block connections of others, even make them fail silently, 
that creates a situation in which other software can't be made
to work correctly. 

Ciao,

-- 
FA

Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.

1326023976.18991_0.ltw:2,a <20120108115926.GD29626 at linuxaudio dot org>