[Python-checkins] CVS: distutils/doc/inst inst.tex,1.14,1.15

[Greg Ward]

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

Modified Files:
	inst.tex 
Log Message:
Fixed a grab-bag of typos spotted by Detlef Lannert.

Index: inst.tex
===================================================================
RCS file: /cvsroot/python/distutils/doc/inst/inst.tex,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -r1.14 -r1.15
*** inst.tex	2000/05/30 03:00:43	1.14
--- inst.tex	2000/06/24 01:33:16	1.15
***************
*** 98,104 ****
  
  If you download a module source distribution, you can tell pretty
! quickly if was packaged and distributed in the standard way, i.e. using
! the Distutils.  First, the distribution's name and version number will
! be featured prominently in the name of the downloaded archive, e.g.
  \file{foo-1.0.tar.gz} or \file{widget-0.9.7.zip}.  Next, the archive
  will unpack into a similarly-named directory: \file{foo-1.0} or
--- 98,104 ----
  
  If you download a module source distribution, you can tell pretty
! quickly if it was packaged and distributed in the standard way, i.e.
! using the Distutils.  First, the distribution's name and version number
! will be featured prominently in the name of the downloaded archive, e.g.
  \file{foo-1.0.tar.gz} or \file{widget-0.9.7.zip}.  Next, the archive
  will unpack into a similarly-named directory: \file{foo-1.0} or
***************
*** 127,131 ****
  be made is, ``Read the module's own installation instructions.''
  
! However, if such instructions exists at all, they are often woefully
  inadequate and targeted at experienced Python developers.  Such users
  are already familiar with how the Python library is laid out on their
--- 127,131 ----
  be made is, ``Read the module's own installation instructions.''
  
! However, if such instructions exist at all, they are often woefully
  inadequate and targeted at experienced Python developers.  Such users
  are already familiar with how the Python library is laid out on their
***************
*** 422,426 ****
  known cases where the prefix scheme will be useful.
  
! First, consider that many Linux distribution put Python in \file{/usr},
  rather than the more traditional \file{/usr/local}.  This is entirely
  appropriate, since in those cases Python is part of ``the system''
--- 422,426 ----
  known cases where the prefix scheme will be useful.
  
! First, consider that many Linux distributions put Python in \file{/usr},
  rather than the more traditional \file{/usr/local}.  This is entirely
  appropriate, since in those cases Python is part of ``the system''
***************
*** 559,563 ****
  the installation base directory (your home directory, in this case):
  \begin{verbatim}
! python setup.py install --home --install-scripts=scripts
  \end{verbatim}
  
--- 559,563 ----
  the installation base directory (your home directory, in this case):
  \begin{verbatim}
! python setup.py install --home=~ --install-scripts=scripts
  \end{verbatim}
  
***************
*** 607,611 ****
  python setup.py install --home=~/python \
                          --install-purelib=lib \
!                         --install-platlib=lib.$PLAT \
                          --install-scripts=scripts
                          --install-data=data
--- 607,611 ----
  python setup.py install --home=~/python \
                          --install-purelib=lib \
!                         --install-platlib='lib.$PLAT' \
                          --install-scripts=scripts
                          --install-data=data