public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Mueller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pms:eapi-5 commit in: /
Date: Sun, 12 Aug 2012 12:11:23 +0000 (UTC)	[thread overview]
Message-ID: <1344764700.c54f758c521714561f0ca94d7d185f516b79df59.ulm@gentoo> (raw)

commit:     c54f758c521714561f0ca94d7d185f516b79df59
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 12 09:45:00 2012 +0000
Commit:     Ulrich Mueller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Aug 12 09:45:00 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=c54f758c

Merge branch 'master' into eapi-5

Conflicts:
	ebuild-vars.tex
	pms.tex


 credits.tex          |   14 +++-----
 ebuild-vars.tex      |   92 +++++++++++++++++++++++++-------------------------
 pkg-mgr-commands.tex |    2 +-
 pms.cls              |   17 +--------
 pms.tex              |   21 +++++++++++
 5 files changed, 75 insertions(+), 71 deletions(-)

diff --cc ebuild-vars.tex
index a4586bf,1dadc35..7eaabc5
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@@ -34,27 -60,24 +60,25 @@@ Ebuilds may define any of the followin
      \t{IUSE} defaults, any use flag name in \t{IUSE} may be prefixed by at most one of a plus or a
      minus sign. If such a prefix is present, the package manager may use it as a suggestion as to
      the default value of the use flag if no other configuration overrides it.
- \item[KEYWORDS] A whitespace separated list of keywords for the ebuild. Each token must be a
-     valid keyword name, as per section~\ref{sec:keyword-names}. May include \t{-*}, which
-     indicates that the package will only work on explicitly listed archs. May include \t{-arch},
-     which indicates that the package will not work on the specified arch. May be empty, which
-     indicates uncertain functionality on any architecture. May be defined in an eclass.
- \item[LICENSE] The package's license. Each text token must correspond to a tree ``licenses/'' entry
-     (see section~\ref{sec:licenses-dir}). See section~\ref{sec:dependencies} for full syntax.
-     May be defined by an eclass. \label{ebuild-var-LICENSE}
- \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.
-     May be defined by an eclass. See section~\ref{sec:dependencies} for full syntax.
+ \item[REQUIRED\_USE] \featurelabel{required-use} Zero or more assertions that must be met by the
+     configuration of \t{USE} flags to be valid for this ebuild. See section~\ref{sec:required-use}
+     for description and section~\ref{sec:dependencies} for full syntax. Only in EAPIs listed in
+     table~\ref{tab:optional-vars-table} as supporting \t{REQUIRED\_USE}.
+ \item[PROPERTIES] \featurelabel{properties} Zero or more properties for this package.
+     See section~\ref{sec:properties} for value meanings and section~\ref{sec:dependencies} for full
+     syntax. For EAPIs listed in table~\ref{tab:optional-vars-table} as having optional support,
+     ebuilds must not rely upon the package manager recognising or understanding this variable in
+     any way.
+ \item[RESTRICT] Zero or more behaviour restrictions for this package. See section~\ref{sec:restrict}
+     for value meanings and section~\ref{sec:dependencies} for full syntax.
+ \item[DEPEND] See section~\ref{sec:dependencies}.
+ \item[RDEPEND] See section~\ref{sec:dependencies}. For some EAPIs, \t{RDEPEND} has special behaviour
+     for its value if unset and when used with an eclass. See section~\ref{sec:rdepend-depend} for
+     details.
+ \item[PDEPEND] See section~\ref{sec:dependencies}.
  \end{description}
  
- If any of these variables are undefined, or if any of these variables are set to invalid values,
- the package manager's behaviour is undefined; ideally, an error in one ebuild should not prevent
- operations upon other ebuilds or packages.
- 
 +\ChangeWhenAddingAnEAPI{5}
  \begin{centertable}{EAPIs supporting \t{IUSE} defaults} \label{tab:iuse-defaults-table}
      \begin{tabular}{ l l }
          \toprule
@@@ -71,31 -93,6 +95,7 @@@
      \end{tabular}
  \end{centertable}
  
- \section{Optional Ebuild-defined Variables}
- 
- Ebuilds may define any of the following variables:
- 
- \begin{description}
- \item[DEPEND] See section~\ref{sec:dependencies}.
- \item[EAPI] The EAPI. See below.
- \item[PDEPEND] See section~\ref{sec:dependencies}.
- \item[RDEPEND] See section~\ref{sec:dependencies}. For some EAPIs, \t{RDEPEND} has special behaviour
-     for its value if unset and when used with an eclass. See section~\ref{sec:rdepend-depend} for
-     details.
- \item[RESTRICT] Zero or more behaviour restrictions for this package. See section~\ref{sec:restrict}
-     for value meanings and section~\ref{sec:dependencies} for full syntax.
- \item[PROPERTIES] \featurelabel{properties} Zero or more properties for this package. See
-     section~\ref{sec:properties} for value meanings and section~\ref{sec:dependencies} for full
-     syntax. For EAPIs listed in table~\ref{tab:optional-vars-table} as having optional support,
-     ebuilds must not rely upon the package manager recognising or understanding this variable in
-     any way.
- \item[REQUIRED\_USE] \featurelabel{required-use} Zero or more assertions that must be met by the
-     configuration of \t{USE} flags to be valid for this ebuild. See section~\ref{sec:required-use}
-     for description and section~\ref{sec:dependencies} for full syntax. Only in EAPIs listed in
-     table~\ref{tab:optional-vars-table} as supporting \t{REQUIRED\_USE}.
- \end{description}
- 
 +\ChangeWhenAddingAnEAPI{5}
  \begin{centertable}{EAPIs supporting various ebuild-defined variables}
  \label{tab:optional-vars-table}
      \begin{tabular}{ l l l }
diff --cc pms.tex
index d0ceda2,7244be9..5885c9c
--- a/pms.tex
+++ b/pms.tex
@@@ -1,8 -1,26 +1,29 @@@
  \documentclass{pms}
  
+ \title{Package Manager Specification}
+ \author{%
+     Stephen P. Bennett \\
+     \href{mailto:spb@exherbo.org}{spb@exherbo.org}
+     \and
+     Christian Faulhammer \\
+     \href{mailto:fauli@gentoo.org}{fauli@gentoo.org}
+     \and
+     Ciaran McCreesh \\
+     \href{mailto:ciaran.mccreesh@googlemail.com}{ciaran.mccreesh@googlemail.com}
+     \and
+     Ulrich Müller \\
+     \href{mailto:ulm@gentoo.org}{ulm@gentoo.org}
+ }
+ \hypersetup{%
+     pdftitle={Package Manager Specification},
+     pdfauthor={Stephen P. Bennett, Christian Faulhammer, Ciaran McCreesh, Ulrich Müller},
+     pdfsubject={Defining a feature set for package managers in the Gentoo world},
+     pdfkeywords={Gentoo, package manager, specification},
+ }
+ 
 +\CurrentEAPIIs{5}
 +\ChangeWhenAddingAnEAPI{5}
 +
  \begin{document}
  \maketitle
  


             reply	other threads:[~2012-08-12 12:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12 12:11 Ulrich Mueller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-11 20:41 [gentoo-commits] proj/pms:eapi-5 commit in: / Ulrich Mueller
2012-09-11 20:41 Ulrich Mueller
2012-09-09 19:54 Ulrich Mueller
2012-09-04  8:58 Ulrich Mueller
2012-08-31 16:16 Ulrich Mueller
2012-08-30 19:50 Ulrich Mueller
2012-08-30 18:20 Ulrich Mueller
2012-08-29 12:03 Ulrich Mueller
2012-08-29 12:03 Ulrich Mueller
2012-08-17  6:46 Ulrich Mueller
2012-08-16 19:51 Ulrich Mueller
2012-08-14  5:56 Ulrich Mueller
2012-08-12 12:11 Ulrich Mueller
2012-08-12 12:11 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 10:13 Ulrich Mueller
2012-05-13  7:48 Ulrich Mueller
2012-05-13  7:30 Ulrich Mueller
2012-05-10  7:20 Ulrich Mueller
2012-05-10  7:17 Ulrich Mueller
2012-05-10  7:17 Ulrich Mueller
2012-05-10  7:00 Ulrich Mueller
2012-05-08 20:09 Ulrich Mueller
2012-05-07 13:27 Ciaran McCreesh

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=1344764700.c54f758c521714561f0ca94d7d185f516b79df59.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@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