From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] [PATCH] SRC_URI may be defined by an eclass.
Date: Tue, 4 Jan 2011 14:01:58 +0100 [thread overview]
Message-ID: <19747.6726.992068.345982@a1i15.kph.uni-mainz.de> (raw)
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@gentoo.org>
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
next reply other threads:[~2011-01-04 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 13:01 Ulrich Mueller [this message]
2011-01-08 10:52 ` [gentoo-pms] [PATCH] SRC_URI may be defined by an eclass Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19747.6726.992068.345982@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-pms@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox