[Python-checkins] CVS: distutils/doc/inst inst.tex,1.17,1.18

[Greg Ward]

Update of /cvsroot/python/distutils/doc/inst
In directory slayer.i.sourceforge.net:/tmp/cvs-serv15274

Modified Files:
	inst.tex 
Log Message:
Minor tweaks to get rid of some '\XXX' remarks.

Index: inst.tex
===================================================================
RCS file: /cvsroot/python/distutils/doc/inst/inst.tex,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -r1.17 -r1.18
*** inst.tex	2000/08/31 16:36:31	1.17
--- inst.tex	2000/09/11 00:33:15	1.18
***************
*** 199,212 ****
  On Mac~OS, ... \XXX{again, how do you run Python scripts on Mac~OS?}
  
- \XXX{arg, my lovely ``bslash'' macro doesn't work in non-tt fonts! help
-   me \LaTeX, you're my only hope...}
  
- 
  \subsection{Splitting the job up}
  
  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.  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
--- 199,209 ----
  On Mac~OS, ... \XXX{again, how do you run Python scripts on Mac~OS?}
  
  
  \subsection{Splitting the job up}
  
  Running \code{setup.py install} builds and installs all modules in one
! run.  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.  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
***************
*** 221,229 ****
  \end{verbatim}
  (If you do this, you will notice that running the \command{install}
! command first runs the \command{build} command, which quickly notices
! that it has nothing to do, since everything in the \file{build}
! directory is up-to-date.)
  
! \XXX{concrete reason for splitting things up?}
  
  
--- 218,230 ----
  \end{verbatim}
  (If you do this, you will notice that running the \command{install}
! command first runs the \command{build} command, which---in this
! case---quickly notices that it has nothing to do, since everything in
! the \file{build} directory is up-to-date.)
  
! You may not need this ability to break things down often if all you do
! is install modules downloaded off the 'net, but it's very handy for more
! advanced tasks.  If you get into distributing your own Python modules
! and extensions, you'll run lots of individual Distutils commands on
! their own.