From 3e7b133c957d92b2f0db6e7060bf8a48617f8d9d Mon Sep 17 00:00:00 2001 From: Greg Ward Date: Tue, 30 May 2000 03:00:43 +0000 Subject: [PATCH] Added concrete example of when separate build and install might be useful (suggested by Moshe Zadka). --- Doc/inst/inst.tex | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Doc/inst/inst.tex b/Doc/inst/inst.tex index 0792c91561d..c7da3dd9aa0 100644 --- a/Doc/inst/inst.tex +++ b/Doc/inst/inst.tex @@ -198,7 +198,11 @@ On Mac~OS, ... \XXX{again, how do you run Python scripts on Mac~OS?} Running \code{setup.py install} builds and installs all modules in one fell swoop. If you prefer to work incrementally---especially useful if you want to customize the build process, or if things are going -wrong---you can use the setup script to do one thing at a time. +wrong---you can use the setup script to do one thing at a time. This is +particularly helpful when the build and install will be done by +different users---e.g., you might want to build a module distribution +and hand it off to a system administrator for installation (or do it +yourself, with super-user privileges). For example, you can build everything in one step, and then install everything in a second step, by invoking the setup script twice: