From 50699d9114a22db66f41f12e488a21de7b25fd39 Mon Sep 17 00:00:00 2001
From: kpetersn <kmpeters@anl.gov>
Date: Thu, 2 Mar 2023 21:14:53 +0000
Subject: [PATCH] Added a question to the FAQ about the use of ~ in paths in
 the solution branch.

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index c8bc546..7db78f7 100644
--- a/README.md
+++ b/README.md
@@ -54,6 +54,12 @@ No.  Just use **mkioc**.
 
 No.
 
+#### Why does the solution branch use ~ instead of /home/beams/USERNAME in the solution branch?
+
+The solution branch uses `~` instead of `/home/beams/USERNAME` in paths because it was the only way to make the solution branch build for everyone without requiring files to be edited.
+
+The use of `~` is highly discouraged; only absolute paths should be used in RELEASE files.  A negative side effect of using `~` in the path to `MOTOR_VMC` in the IOC's **RELEASE** file, is that `MOTOR_VMC` doesn't appear in the IOC's **envPaths** file.  This wasn't a problem during the training becase the IOC doesn't load anything from the motorVMC module at runtime.
+
 ## The solution branch
 
 Both the xxx and motorVMC repos have a **solution** branch with tags for each step that:
-- 
GitLab