From: Thomas Walker Lynch <eknp9n@reasoningtechnology.com>
Date: Mon, 13 Oct 2025 11:03:21 +0000 (+0000)
Subject: replaces customized with diff patches
X-Git-Url: https://git.reasoningtechnology.com/style/static/gitweb.js?a=commitdiff_plain;h=446d95783dcfcb98bbe8096cf09ac0f217362ab7;p=Harmony.git

replaces customized with diff patches
---

diff --git a/tool_shared/customized/.githolder b/tool_shared/customized/.githolder
deleted file mode 100644
index e69de29..0000000
diff --git a/tool_shared/document/install_generic.org b/tool_shared/document/install_generic.org
new file mode 100644
index 0000000..c02d1d3
--- /dev/null
+++ b/tool_shared/document/install_generic.org
@@ -0,0 +1,82 @@
+
+This is the generic install.org doc that comes with the skeleton.
+
+1. $REPO_HOME/tool_shared/third_party/.gitignore:
+
+    * 
+    !/.gitignore
+    !/patch
+
+  The only things from the third party directory that will be pushed to the repo origin is the .gitignore file and the patches.
+
+
+2. downloaded tar files etc. go into the directory `upstream`
+
+    $REPO_HOME/tool_shared/upstream
+ 
+   Typically the contents of upstream are deleted after the install.
+
+3. for the base install
+
+     cd $REPO_HOME/tool_shared/third_party
+     do whatever it takes to install tool, as examples:
+       git clone <tool_path>
+       tar -xzf ../upstream/tar
+       ...
+
+   Be sure to add the path to the tool executable(s) in the $REPO_HOME/env_$ROLE files for the $ROLE who uses the tool.
+
+   Assuming you are not also developing the tool, for safety
+   change each installed git project to a local branch:
+
+     b=<site>_<project>_local_$USER
+     git switch -c "$b"
+   
+
+4. Define some variables to simplify our discussion. Lowercase variable names
+   are not exported from the shell.
+
+     # already set in the environment
+     #   REPO_HOME
+     #   PROJECT
+     #   USER
+
+     tool=<tool-name>  # e.g., RT_gcc
+     tool_dpath="$REPO_HOME/tool_shared/third_party/$tool"
+     patch_dpath="$REPO_HOME/tool_shared/third_party/patch/"
+
+
+5. create a patch series (from current vendor state → your local edits)
+
+   # this can be repeated and will create an encompassing diff file
+
+   # optionally crate a new branch after cloning the repo and work from there.
+   # You won't make any commits, but in case you plan to check these in ever,
+   # or have a ommits burned into your brain-stem, this will help.
+
+   # make changes
+
+     cd "$tool_dpath"
+
+     # do your edits
+
+     # Stage edits. Do not commit them!!  Be sure you are in the third party
+     # tool directory, or the changes will go to the project.
+     git add -A
+
+     # diff the stage from the current repo to create the patch file
+     git diff --staged > "$patch_dpath/$tool"
+
+
+6. how to apply an existing patch
+
+   Get a fresh clone of the tool into $tool_dpath.
+
+     cd "$tool_dpath"
+     git apply "$patch_dpath/$tool"
+
+   You can see what `git apply` would do by running 
+
+     git apply --check /path/to/your/patch_dpath/$tool
+
+   
diff --git a/tool_shared/patch/.githolder b/tool_shared/patch/.githolder
new file mode 100644
index 0000000..e69de29