Constrain SNAP_CONFINE_DEBUG values #158

Merged
merged 1 commit into from Oct 16, 2016

Conversation

Projects
None yet
2 participants
Collaborator

zyga commented Sep 28, 2016

This patch changes how the aforementioned environment variable is
interpreted. To have some sanity only a subset of values now triggers
the debugging semantics. Specifically only "yes" and "1" do so, other
values are handled gracefully (e.g. unset, empty, "no" or "0") and
finally all other values result in a diagnostic message.

Signed-off-by: Zygmunt Krynicki zygmunt.krynicki@canonical.com

Constrain SNAP_CONFINE_DEBUG values
This patch changes how the aforementioned environment variable is
interpreted. To have some sanity only a subset of values now triggers
the debugging semantics. Specifically only "yes" and "1" do so, other
values are handled gracefully (e.g. unset, empty, "no" or "0") and
finally all other values result in a diagnostic message.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>

Looks good to me!

@zyga zyga merged commit f344778 into master Oct 16, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@zyga zyga deleted the sane-bool-getenv branch Oct 16, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment