>> contributor, and if the internal API changes (as has happened between >> 0.80 and 0.90) and the driver is not ported, it will be removed from >> the Makefiles. > >That may be clear to the driver writers, but it won't make any sense >to users filing bug reports in Mantis because one of our supported >features doesn't work on their hardware.
what kinds of features are you thinking of? most of the hardware-related features derive from the ALSA driver, not JACK itself. > If you really want to wash >your hands of all responsibility for this code, it needs to come from >some other package, *not* from JACK CVS. that would be fine with me. we can package jack-audio-connection-kit with just the core supported drivers (whatever they may be) and then jack-audio-connection-kit-<foo> for other drivers. its a trivial change to the Makefiles that i know taybin will love to do :) --p