Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 3e7b133

Browse files
committed
Added concrete example of when separate build and install might be
useful (suggested by Moshe Zadka).
1 parent 9815011 commit 3e7b133

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

Doc/inst/inst.tex

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,11 @@ \subsection{Splitting the job up}
198198
Running \code{setup.py install} builds and installs all modules in one
199199
fell swoop. If you prefer to work incrementally---especially useful if
200200
you want to customize the build process, or if things are going
201-
wrong---you can use the setup script to do one thing at a time.
201+
wrong---you can use the setup script to do one thing at a time. This is
202+
particularly helpful when the build and install will be done by
203+
different users---e.g., you might want to build a module distribution
204+
and hand it off to a system administrator for installation (or do it
205+
yourself, with super-user privileges).
202206

203207
For example, you can build everything in one step, and then install
204208
everything in a second step, by invoking the setup script twice:

0 commit comments

Comments
 (0)