[Python-checkins] CVS: distutils/doc/dist dist.tex,1.10,1.11

Fri, 28 Apr 2000 13:12:27 -0400 (EDT)

Update of /projects/cvsroot/distutils/doc/dist
In directory thrak:/home/gward/python/distutils/doc/dist

Modified Files:
	dist.tex 
Log Message:
Stripped leading 'sec:' from all section labels -- generates bad filenames,
bad link URLs in HTML, etc.

Index: dist.tex
===================================================================
RCS file: /projects/cvsroot/distutils/doc/dist/dist.tex,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -r1.10 -r1.11
*** dist.tex	2000/04/25 02:57:36	1.10
--- dist.tex	2000/04/28 17:12:24	1.11
***************
*** 16,20 ****

  \section{Introduction}
! \label{sec:intro}

  In the past, Python module developers have not had much infrastructure
--- 16,20 ----

  \section{Introduction}
! \label{intro}

  In the past, Python module developers have not had much infrastructure
***************
*** 39,43 ****

  \section{Concepts \& Terminology}
! \label{sec:concepts}

  Using the Distutils is quite simple, both for module developers and for
--- 39,43 ----

  \section{Concepts \& Terminology}
! \label{concepts}

  Using the Distutils is quite simple, both for module developers and for
***************
*** 66,70 ****

  \subsection{A simple example}
! \label{sec:simple-example}

  The setup script is usually quite simple, although since it's written in
--- 66,70 ----

  \subsection{A simple example}
! \label{simple-example}

  The setup script is usually quite simple, although since it's written in
***************
*** 141,145 ****

  \subsection{General Python terminology}
! \label{sec:python-terms}

  If you're reading this document, you probably have a good idea of what
--- 141,145 ----

  \subsection{General Python terminology}
! \label{python-terms}

  If you're reading this document, you probably have a good idea of what
***************
*** 168,172 ****

  \subsection{Distutils-specific terminology}
! \label{sec:distutils-term}

  The following terms apply more specifically to the domain of
--- 168,172 ----

  \subsection{Distutils-specific terminology}
! \label{distutils-term}

  The following terms apply more specifically to the domain of
***************
*** 193,197 ****

  \section{Writing the Setup Script}
! \label{sec:setup-script}

  The setup script is the centre of all activity in building,
--- 193,197 ----

  \section{Writing the Setup Script}
! \label{setup-script}

  The setup script is the centre of all activity in building,
***************
*** 199,203 ****
  purpose of the setup script is to describe your module distribution to
  the Distutils, so that the various commands that operate on your modules
! do the right thing.  As we saw in section~\ref{sec:simple-example}
  above, the setup script consists mainly of a call to \function{setup()},
  and all information supplied to the Distutils is suppled as keyword
--- 199,203 ----
  purpose of the setup script is to describe your module distribution to
  the Distutils, so that the various commands that operate on your modules
! do the right thing.  As we saw in section~\ref{simple-example}
  above, the setup script consists mainly of a call to \function{setup()},
  and all information supplied to the Distutils is suppled as keyword
***************
*** 226,230 ****
  \end{verbatim}
  There are only two differences between this and the trivial one-file
! distribution presented in section~\ref{sec:simple-example}: more
  meta-data, and the specification of pure Python modules by package,
  rather than by module.  This is important since the Distutils consist of
--- 226,230 ----
  \end{verbatim}
  There are only two differences between this and the trivial one-file
! distribution presented in section~\ref{simple-example}: more
  meta-data, and the specification of pure Python modules by package,
  rather than by module.  This is important since the Distutils consist of
***************
*** 246,250 ****

  \subsection{Package directories}
! \label{sec:package-dirs}

  The \option{packages} option tells the Distutils to process (build,
--- 246,250 ----

  \subsection{Package directories}
! \label{package-dirs}

  The \option{packages} option tells the Distutils to process (build,
***************
*** 293,302 ****

  \subsection{Listing individual modules}
! \label{sec:listing-modules}

  For a small module distribution, you might prefer to list all modules
  rather than listing packages---especially the case of a single module
  that goes in the ``root package'' (i.e., no package at all).  This
! simplest case was shown in section~\ref{sec:simple-example}; here is a
  slightly more involved example:
  \begin{verbatim}
--- 293,302 ----

  \subsection{Listing individual modules}
! \label{listing-modules}

  For a small module distribution, you might prefer to list all modules
  rather than listing packages---especially the case of a single module
  that goes in the ``root package'' (i.e., no package at all).  This
! simplest case was shown in section~\ref{simple-example}; here is a
  slightly more involved example:
  \begin{verbatim}
***************
*** 313,317 ****

  \section{Writing the Setup Configuration File}
! \label{sec:setup-config}

  \XXX{not implemented yet!}
--- 313,317 ----

  \section{Writing the Setup Configuration File}
! \label{setup-config}

  \XXX{not implemented yet!}
***************
*** 339,345 ****

  \section{Creating a Source Distribution}
! \label{sec:source-dist}

! As shown in section~\ref{sec:simple-example}, you use the
  \command{sdist} command to create a source distribution.  In the
  simplest case,
--- 339,345 ----

  \section{Creating a Source Distribution}
! \label{source-dist}

! As shown in section~\ref{simple-example}, you use the
  \command{sdist} command to create a source distribution.  In the
  simplest case,
***************
*** 377,381 ****

  \subsection{The manifest and manifest template}
! \label{sec:manifest}

  Without any additional information, the \command{sdist} command puts a
--- 377,381 ----

  \subsection{The manifest and manifest template}
! \label{manifest}

  Without any additional information, the \command{sdist} command puts a
***************
*** 415,419 ****
  exclude all directories matching \code{examples/sample?/build}.  There
  are several other commands available in the manifest template
! mini-language; see section~\ref{sec:sdist-cmd}.

  The order of commands in the manifest template very much matters:
--- 415,419 ----
  exclude all directories matching \code{examples/sample?/build}.  There
  are several other commands available in the manifest template
! mini-language; see section~\ref{sdist-cmd}.

  The order of commands in the manifest template very much matters:
***************
*** 455,459 ****

  \subsection{Manifest-related options}
! \label{sec:manifest-options}

  The normal course of operations for the \command{sdist} command is as
--- 455,459 ----

  \subsection{Manifest-related options}
! \label{manifest-options}

  The normal course of operations for the \command{sdist} command is as
***************
*** 494,498 ****

  \section{Creating Built Distributions}
! \label{sec:built-dist}

  A ``built distribution'' is what you're probably used to thinking of
--- 494,498 ----

  \section{Creating Built Distributions}
! \label{built-dist}

  A ``built distribution'' is what you're probably used to thinking of
***************
*** 595,615 ****

  \section{Examples}
! \label{sec:examples}

  \subsection{Pure Python distribution (by module)}
! \label{sec:pure-mod}

  \subsection{Pure Python distribution (by package)}
! \label{sec:pure-pkg}

  \subsection{Single extension module}
! \label{sec:single-ext}

  \subsection{Multiple extension modules}
! \label{sec:multiple-ext}

--- 595,615 ----

  \section{Examples}
! \label{examples}

  \subsection{Pure Python distribution (by module)}
! \label{pure-mod}

  \subsection{Pure Python distribution (by package)}
! \label{pure-pkg}

  \subsection{Single extension module}
! \label{single-ext}

  \subsection{Multiple extension modules}
! \label{multiple-ext}

***************
*** 619,664 ****

  \section{Extending the Distutils}
! \label{sec:extending}

  \subsection{Extending existing commands}
! \label{sec:extend-existing}

  \subsection{Writing new commands}
! \label{sec:new-commands}

  \section{Reference}
! \label{sec:ref}

  \subsection{Building modules: the \protect\command{build} command family}
! \label{sec:build-cmds}

  \subsubsection{\protect\command{build}}
! \label{sec:build-cmd}

  \subsubsection{\protect\command{build\_py}}
! \label{sec:build-py-cmd}

  \subsubsection{\protect\command{build\_ext}}
! \label{sec:build-ext-cmd}

  \subsubsection{\protect\command{build\_clib}}
! \label{sec:build-clib-cmd}

  \subsection{Installing modules: the \protect\command{install} command family}
! \label{sec:install-cmd}

  \subsection{Cleaning up: the \protect\command{clean} command}
! \label{sec:clean-cmd}

  \subsection{Creating a source distribution: the \protect\command{sdist} command}
! \label{sec:sdist-cmd}

--- 619,664 ----

  \section{Extending the Distutils}
! \label{extending}

  \subsection{Extending existing commands}
! \label{extend-existing}

  \subsection{Writing new commands}
! \label{new-commands}

  \section{Reference}
! \label{ref}

  \subsection{Building modules: the \protect\command{build} command family}
! \label{build-cmds}

  \subsubsection{\protect\command{build}}
! \label{build-cmd}

  \subsubsection{\protect\command{build\_py}}
! \label{build-py-cmd}

  \subsubsection{\protect\command{build\_ext}}
! \label{build-ext-cmd}

  \subsubsection{\protect\command{build\_clib}}
! \label{build-clib-cmd}

  \subsection{Installing modules: the \protect\command{install} command family}
! \label{install-cmd}

  \subsection{Cleaning up: the \protect\command{clean} command}
! \label{clean-cmd}

  \subsection{Creating a source distribution: the \protect\command{sdist} command}
! \label{sdist-cmd}

***************
*** 695,699 ****
  \subsection{Creating a ``built'' distribution: the
    \protect\command{bdist} command family}
! \label{sec:bdist-cmds}

--- 695,699 ----
  \subsection{Creating a ``built'' distribution: the
    \protect\command{bdist} command family}
! \label{bdist-cmds}