Currently, the depqbfPath function only passes --qdo to the depqbf executable. This works well enough for versions of depqbf prior to 6.03. In version 6.03, however, depqbf also requires the use of the --no-dynamic-nenofex flag (see this comment). What's more, this flag is not backwards-compatible with pre-6.03 versions, as passing the flag to older versions will result in an error.
This results in an unfortunate situation where depqbfPath—which ideally should just do the right thing for most users—will only do the right thing for old versions of depqbfPath. For newer versions, ersatz users have no choice but to manually specify --no-dynamic-nenofex, like what was done in #93. We ought to do better, and I think we can. I propose that:
Before invoking depqbf, we query its version (via depqbf --version).
If its version is 6.03 or greater, call depqbf with --no-dynamic-nenofex. Otherwise, call depqbf without it.
I have no idea how stable the output of depqbf --version is, but I hope it is stable enough to rely on.
Currently, the
depqbfPathfunction only passes--qdoto thedepqbfexecutable. This works well enough for versions ofdepqbfprior to 6.03. In version 6.03, however,depqbfalso requires the use of the--no-dynamic-nenofexflag (see this comment). What's more, this flag is not backwards-compatible with pre-6.03 versions, as passing the flag to older versions will result in an error.This results in an unfortunate situation where
depqbfPath—which ideally should just do the right thing for most users—will only do the right thing for old versions ofdepqbfPath. For newer versions,ersatzusers have no choice but to manually specify--no-dynamic-nenofex, like what was done in #93. We ought to do better, and I think we can. I propose that:depqbf, we query its version (viadepqbf --version).6.03or greater, calldepqbfwith--no-dynamic-nenofex. Otherwise, calldepqbfwithout it.I have no idea how stable the output of
depqbf --versionis, but I hope it is stable enough to rely on.