From 37adb811e9b28b06d958ea7183e85b46f384c0cd Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Mon, 21 Mar 2022 11:24:56 +0530
Subject: doc: Clarify double reference of (guix build utils).

* doc/forge.skb (Tutorial): Clarify double reference of (guix build
utils).
---
 doc/forge.skb | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/forge.skb b/doc/forge.skb
index 68fa2a4..5c388b1 100644
--- a/doc/forge.skb
+++ b/doc/forge.skb
@@ -105,6 +105,15 @@ using ,(code [with-imported-modules]). In addition, it needs a number
 of packages which we make available using ,(code [with-packages]). And
 finally, within the body of the G-expression, we have commands cloning
 the git repository, building the source and running the tests.])
+    (p [The attentive reader may notice what looks like ,(code [(guix
+build utils)]) being referenced twice—once with ,(code
+[with-imported-modules]) and again with ,(code [use-modules]). This is
+not a mistake. G-expressions are serialized into Guile scripts. ,(code
+[with-imported-modules]) ensures that code for ,(code [(guix build
+utils)]) is available and is in the ,(ref :url
+"https://www.gnu.org/software/guile/manual/html_node/Load-Paths.html"
+:text "load path"). ,(code [use-modules]) actually imports ,(code
+[(guix build utils)]) when the script runs.])
     (prog (source :language scheme
                   :file "doc/snippets/tutorial.scm"
                   :start 11 :stop 22)
-- 
cgit v1.2.3