Section "Mandatory Ebuild-defined Variables" says "may be defined by a
eclass" for all variables except IUSE and SRC_URI. Was this simply
overlooked for SRC_URI, or is it on purpose?

Ulrich


From 071955e0bcd73a7634dd792a532e8052a8d28d81 Mon Sep 17 00:00:00 2001
From: Ulrich Mueller <ulm@g.o>
Date: Tue, 4 Jan 2011 14:02:08 +0100
Subject: [PATCH] SRC_URI may be defined by an eclass.

---
 ebuild-vars.tex |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index db4d50d..0af3540 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -45,9 +45,9 @@ All ebuilds must define at least the following variables:
 \item[SLOT] The package's slot. Must be a valid slot name, as per section~\ref{sec:slot-names}. May
     be defined by an eclass. Must not be empty.
 \item[SRC\_URI] A list of source URIs for the package. Valid protocols are \t{http://},
-    \t{https://}, \t{ftp://} and \t{mirror://} (see section~\ref{sec:thirdpartymirrors} for mirror behaviour).
-    Fetch restricted packages may include URL parts consisting of just a filename. See
-    section~\ref{sec:dependencies} for full syntax.
+    \t{https://}, \t{ftp://} and \t{mirror://} (see section~\ref{sec:thirdpartymirrors} for mirror
+    behaviour). Fetch restricted packages may include URL parts consisting of just a filename.
+    May be defined by an eclass. See section~\ref{sec:dependencies} for full syntax.
 \end{description}
 
 If any of these variables are undefined, or if any of these variables are set to invalid values,
-- 
1.7.3.4