Right now, the 'Commands provided by package dependencies' section
contradicts the changes done in 'Dependency classes' lately. Remove
the contradicting (and not really useful) information with a reference
to the latter section.
---
 dependencies.tex        |    1 +
 ebuild-env-commands.tex |   12 ++----------
 2 files changed, 3 insertions(+), 10 deletions(-)

diff --git a/dependencies.tex b/dependencies.tex
index 5bdad39..abcb820 100644
--- a/dependencies.tex
+++ b/dependencies.tex
@@ -2,6 +2,7 @@
 \label{sec:dependencies}
 
 \section{Dependency Classes}
+\label{sec:dependency-classes}
 
 \begin{centertable}{Dependency classes required to be satisfied for a particular phase function} \label{tab:phase-function-dependency-classes}
     \begin{tabular}{ p{0.2\textwidth} p{0.7\textwidth} }
diff --git a/ebuild-env-commands.tex b/ebuild-env-commands.tex
index cad0bda..78e33a2 100644
--- a/ebuild-env-commands.tex
+++ b/ebuild-env-commands.tex
@@ -34,16 +34,8 @@ The following commands must always be available in the ebuild environment:
 \subsection{Commands provided by package dependencies}
 
 In some cases a package's build process will require the availability of executables not provided by
-the core system, a common example being autotools. Commands provided by dependencies are available
-in the following cases:
-\begin{compactitem}
-\item In the \t{src} phases, any command provided by a package listed in \t{DEPEND} is available.
-\item In the \t{pkg} phases, at least one of the following conditions must be met:
-    \begin{compactitem}
-    \item Any command provided by a package listed in \t{DEPEND} is available.
-    \item Any command provided by a package listed in \t{RDEPEND} is available.
-    \end{compactitem}
-\end{compactitem}
+the core system, a common example being autotools. The availability of commands provided by the
+particular types of dependencies is explained in section~\ref{sec:dependency-classes}.
 
 \subsection{Ebuild-specific Commands}
 \input{pkg-mgr-commands.tex}
-- 
1.7.5.3