[Python-checkins] CVS: distutils/doc/inst inst.tex,1.19,1.20

[Greg Ward]

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

Modified Files:
	inst.tex 
Log Message:
Changed/added a bunch of section labels so HTML files will be named nicely.

Index: inst.tex
===================================================================
RCS file: /cvsroot/python/distutils/doc/inst/inst.tex,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -r1.19 -r1.20
*** inst.tex	2000/09/12 23:55:19	1.19
--- inst.tex	2000/09/13 00:00:58	1.20
***************
*** 76,80 ****
  
  \subsection{Best case: trivial installation}
! \label{trivial-inst}
  
  In the best case, someone will have prepared a special version of the
--- 76,80 ----
  
  \subsection{Best case: trivial installation}
! \label{trivial-install}
  
  In the best case, someone will have prepared a special version of the
***************
*** 161,165 ****
  
  \section{Standard Build and Install}
! \label{normal-install}
  
  As described in section~\ref{new-standard}, building and installing
--- 161,165 ----
  
  \section{Standard Build and Install}
! \label{standard-install}
  
  As described in section~\ref{new-standard}, building and installing
***************
*** 174,177 ****
--- 174,178 ----
  
  \subsection{Platform variations}
+ \label{platform-variations}
  
  You should always run the setup command from the distribution root
***************
*** 218,221 ****
--- 219,223 ----
  
  \subsection{Splitting the job up}
+ \label{splitting-up}
  
  Running \code{setup.py install} builds and installs all modules in one
***************
*** 247,250 ****
--- 249,253 ----
  
  \subsection{How building works}
+ \label{how-build-works}
  
  As implied above, the \command{build} command is responsible for putting
***************
*** 286,289 ****
--- 289,293 ----
  
  \subsection{How installation works}
+ \label{how-install-works}
  
  After the \command{build} command runs (whether you run it explicitly,
***************
*** 410,414 ****
  
  \subsection{Alternate installation: Unix (the home scheme)}
! \label{alt-unix-prefix}
  
  Under Unix, there are two ways to perform an alternate installation.
--- 414,418 ----
  
  \subsection{Alternate installation: Unix (the home scheme)}
! \label{alt-install-prefix}
  
  Under Unix, there are two ways to perform an alternate installation.
***************
*** 440,444 ****
  
  \subsection{Alternate installation: Unix (the prefix scheme)}
! \label{alt-unix-home}
  
  The ``prefix scheme'' is useful when you wish to use one Python
--- 444,448 ----
  
  \subsection{Alternate installation: Unix (the prefix scheme)}
! \label{alt-install-home}
  
  The ``prefix scheme'' is useful when you wish to use one Python
***************
*** 512,516 ****
  
  \subsection{Alternate installation: Windows}
! \label{alt-windows}
  
  Since Windows has no conception of a user's home directory, and since
--- 516,520 ----
  
  \subsection{Alternate installation: Windows}
! \label{alt-install-windows}
  
  Since Windows has no conception of a user's home directory, and since
***************
*** 535,539 ****
  
  \subsection{Alternate installation: Mac~OS}
! \label{alt-macos}
  
  Like Windows, Mac~OS has no notion of home directories (or even of
--- 539,543 ----
  
  \subsection{Alternate installation: Mac~OS}
! \label{alt-install-macos}
  
  Like Windows, Mac~OS has no notion of home directories (or even of