Open asomers opened 10 years ago
I see what's going on now. kyua.conf(5) specifies that the variable should be called "unprivileged_user", but atf-test-case(4) specifies that it should be called "unprivileged-user". engine/metadata.cpp does the conversion. This violates POLS. Would it be possible to unify the two? There aren't very many ATF test cases in the wild that use that variable, so it should be possible to convert them.
Two thoughts:
unprivileged_user
should be a Kyua-internal variable and not leak to tests. If tests want to use a variable that defines an unprivileged user, they should just define such variable in the scope of their test suite and use that instead. The fact that unprivileged-user
is being passed to ATF test programs is an artifact of what atf-run
did, and the original addition of this functionality was a quick hack without much thought.unprivileged_user
and unprivileged-user
to the tests so that we could execute a controlled deprecation.I'm currently leaning towards doing a.
Four tests in testers/run_test.c require the nonexistent config variable "unprivileged-user". The correct variable, according to kyua.conf(5) and kyua.conf.in from ports, is "unprivileged_user" (underscore instead of hyphen). Patch below: