From f242016a0921f3aeac885b3332acd14fdaf14af1 Mon Sep 17 00:00:00 2001 From: David Holsgrove Date: Thu, 4 Oct 2012 13:26:14 +1000 Subject: scripts/functions: add a generic custom location infrastructure Add a generic custom location infrastructure (inspired by the one in kernel/linux) to allow the user to use custom tarballs or directories for any component. Signed-off-by: "David Holsgrove" [yann.morin.1998@free.fr: move config option, improve help text, fix API doc] Signed-off-by: "Yann E. MORIN" Message-Id: <131c163c69f9cc81d2be.1349931191@localhost.localdomain> PatchWork-Id: 190784 Message-Id: <0bbaba9190a76ba97f72.1349931192@localhost.localdomain> PatchWork-Id: 190785 --- config/global/paths.in | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'config/global') diff --git a/config/global/paths.in b/config/global/paths.in index ed26dfc8..c4d0593e 100644 --- a/config/global/paths.in +++ b/config/global/paths.in @@ -19,6 +19,15 @@ config SAVE_TARBALLS If you say 'y' here, new downloaded tarballs will be saved in the directory you entered above. +config CUSTOM_LOCATION_ROOT_DIR + string + depends on EXPERIMENTAL + prompt "Directory containing custom source components" + help + This is the path CT-NG will attempt to use as a root for locating + local copies of source components (CUSTOM_LOCATION_ROOT_DIR/component) + unless a component declares its own specific custom location. + config WORK_DIR string prompt "Working directory" if ! BACKEND -- cgit v1.2.3