From 5ff076d8adeec81654abbab47b2c871d4b3fdaa2 Mon Sep 17 00:00:00 2001 From: Qyriad Date: Thu, 16 May 2024 14:29:38 -0600 Subject: [PATCH] docs: mention importNative/exec in allow-unsafe-native-code-during-evaluation Both of these still needs their own actual documentation, but they are at least now mentioned that they exist and what they're enabled by. Change-Id: I235b9e8e627e04ed06611423c8e67a8eca233120 --- src/libexpr/eval-settings.hh | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/libexpr/eval-settings.hh b/src/libexpr/eval-settings.hh index 98fe6881e..4674acda2 100644 --- a/src/libexpr/eval-settings.hh +++ b/src/libexpr/eval-settings.hh @@ -14,8 +14,11 @@ struct EvalSettings : Config static std::string resolvePseudoUrl(std::string_view url); - Setting enableNativeCode{this, false, "allow-unsafe-native-code-during-evaluation", - "Whether builtin functions that allow executing native code should be enabled."}; + Setting enableNativeCode{this, false, "allow-unsafe-native-code-during-evaluation", R"( + Whether builtin functions that allow executing native code should be enabled. + + In particular, this adds the `importNative` and `exec` builtins. + )"}; Setting nixPath{ this, getDefaultNixPath(), "nix-path",