[PATCH 04/12] kdevops: introduce KDEVOPS_CONTROLLER_DATA_PATH for controller artefacts

From: Daniel Gomez <[email protected]>

target_linux_dir_path is documented as the path on the target
system; a bootlinux controller mode that runs everything on the
control node should not borrow a variable that pretends to be
the guest's /data mount.

Introduce KDEVOPS_CONTROLLER_DATA_PATH as the controller-side
parallel of data_path: one root under which every controller
artefact lives (cloned source trees, out-of-tree build dirs,
install destdirs, future per-workflow scratch). Default to a
data/ sibling of the kdevops checkout so nothing assumes a
distro-wide /data on the control host.

Generated-by: Claude AI
Signed-off-by: Daniel Gomez <[email protected]>
---
 kconfigs/Kconfig.kdevops | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/kconfigs/Kconfig.kdevops b/kconfigs/Kconfig.kdevops
index 68e91193..499313de 100644
--- a/kconfigs/Kconfig.kdevops
+++ b/kconfigs/Kconfig.kdevops
@@ -77,6 +77,21 @@ config KDEVOPS_CUSTOM_SSH_KEXALGORITHMS
 	  Some distributions, such as older distributions, may require a custom
 	  ssh configuration entry for the KexAlgorithms parameter.
 
+config KDEVOPS_CONTROLLER_DATA_PATH
+	string "Controller-side data path"
+	output yaml
+	default "$(TOPDIR_PATH)/data"
+	help
+	  Absolute path on the control node where kdevops places
+	  controller-side artefacts: source trees for local builds
+	  (bootlinux controller mode clones Linux under here),
+	  out-of-tree build directories, install destdirs, and
+	  workflow scratch space. This is the controller-side parallel
+	  of data_path, which is the target-guest view of the same
+	  concept. Defaults to a data/ sibling of the kdevops checkout
+	  so kdevops does not assume a distro-wide /data mount on the
+	  control host.
+
 config KDEVOPS_MAKE_VERBOSE
 	bool "Enable verbose make output (V=1)"
 	default n

-- 
2.53.0