diff --git a/Divorce-Your-Linux-Admin.rst b/Divorce-Your-Linux-Admin.rst
index 0c1ba56..1e0d609 100644
--- a/Divorce-Your-Linux-Admin.rst
+++ b/Divorce-Your-Linux-Admin.rst
@@ -329,12 +329,30 @@
            tar -czvf /shared/full-linuxbrew.tar.gz /opt/TundraWare/tools
 
 
-You should now be able to install and use this tool tree on a
+Deploying The Tools
++++++++++++++++++++
+
+You should now be able to install and use this tool tree on a new
 docker, VM, or physical Linux instance by doing this::
 
     tar -xzvf /shared/full-linuxbrew.tar.gz -C /
     export PATH="/opt/TundraWare/tools/bin:/opt/TundraWare/tools/sbin:$PATH"
 
+If all you want to do is execute the binaries you've just installed,
+that should be it.
+
+If you also want to be able to install additional packages in the new
+tools instance, you'll need to install system ``perl``, ``automake``,
+etc. as decribed in the prior section.
+
+This is not really a great idea, though.  The better way is to keep a
+master tools configuration on a build server, and add- or delete
+content there as we've just seen.  Then build tarballs for
+distribution via ``tsshbatch`` or ``ansible``.  If each tools instance
+does its own upgrades, when you finally do release a new master
+update, it's likely going to wipe or or conflict with the local
+bespoke version.
+
 
 Gotchas
 -------