On Saturday 17 November 2007, Peter Weller wrote:
> Yes. At least there used to be. I should check to see what the status is
> at the moment. The configure script doesn't(/didn't) know about
> --disable option(s) for at least some of the configuration flags, and
> runtime problems were experienced in some cases. This may or may not be
> fixed now, so I should check it out.

any package that does not operate properly with --{enable,disable}-feature
needs to get fixed. it's usually quite trivial to resolve this in the
configure script and get upstream to fix it.
-mike