From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QVplo-0004jl-BS for garchives@archives.gentoo.org; Sun, 12 Jun 2011 18:52:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 074EA1C002; Sun, 12 Jun 2011 18:52:11 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id ADF971C002 for ; Sun, 12 Jun 2011 18:52:11 +0000 (UTC) Received: from pomiocik.lan (87-205-62-108.adsl.inetia.pl [87.205.62.108]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 5F6F21B4011; Sun, 12 Jun 2011 18:52:10 +0000 (UTC) Date: Sun, 12 Jun 2011 20:52:36 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-pms@lists.gentoo.org Cc: Ciaran McCreesh Subject: Re: [gentoo-pms] Rephrasing *DEPEND Message-ID: <20110612205236.13bbdd4b@pomiocik.lan> In-Reply-To: <20110611125341.185e19d9@googlemail.com> References: <20110611093245.5d9d266c@pomiocik.lan> <20110611125341.185e19d9@googlemail.com> Organization: Gentoo X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Package Manager Specification discussions X-BeenThere: gentoo-pms@gentoo.org X-BeenThere: gentoo-pms@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/XH+PzyxsBHPHTnMzE113Zcs"; protocol="application/pgp-signature" X-Archives-Salt: X-Archives-Hash: 5d1065daffbeddd59093cf703e4f4d16 --Sig_/XH+PzyxsBHPHTnMzE113Zcs Content-Type: multipart/mixed; boundary="MP_/+5BY6.jwkzLv4dkJ79eXeOT" --MP_/+5BY6.jwkzLv4dkJ79eXeOT Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline And here goes another proposal. This time I introduced a table to clearly state phase function <-> dependency class relationships but I guess someone with a taste should look at it and make it look good :P. --=20 Best regards, Micha=C5=82 G=C3=B3rny --MP_/+5BY6.jwkzLv4dkJ79eXeOT Content-Type: text/x-patch Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename=0001-Rephrase-DEPEND-to-state-when-and-whether-they-are-i.patch =46rom e1bce9a316494f14d059b5afc0e1912832622334 Mon Sep 17 00:00:00 2001 From: =3D?UTF-8?q?Micha=3DC5=3D82=3D20G=3DC3=3DB3rny?=3D Date: Sat, 11 Jun 2011 09:32:03 +0200 Subject: [PATCH] Rephrase *DEPEND to state when and whether they are installed. --- dependencies.tex | 27 ++++++++++++++++++++++----- 1 files changed, 22 insertions(+), 5 deletions(-) diff --git a/dependencies.tex b/dependencies.tex index f6318d8..b218579 100644 --- a/dependencies.tex +++ b/dependencies.tex @@ -6,13 +6,30 @@ There are three classes of dependencies supported by ebuilds: =20 \begin{compactitem} -\item Build dependencies (\t{DEPEND}). These must be installed and usable = before the ebuild - is installed. -\item Runtime dependencies (\t{RDEPEND}). These must be installed and usab= le before the ebuild - is treated as usable. -\item Post dependencies (\t{PDEPEND}). These must be installed at some poi= nt. +\item Build dependencies (\t{DEPEND}). These must be installed and usable = before any of + the ebuild \t{src\_*} phase functions is executed. These may not be insta= lled at all + if a binary package is being merged. +\item Runtime dependencies (\t{RDEPEND}). These must be installed and usab= le before + the results of an ebuild merging are treated as usable. +\item Post dependencies (\t{PDEPEND}). These must be installed at some poi= nt before + the package manager finishes the batch of installs. \end{compactitem} =20 +\begin{centertable}{Dependency classes required to be satisfied for a part= icular phase function} \label{tab:phase-function-dependency-classes} + \begin{tabular}{ p{0.2\textwidth} p{0.7\textwidth} } + \toprule + \multicolumn{1}{c}{\textbf{Phase function}} & + \multicolumn{1}{c}{\textbf{Satisfied dependency classes}} \\ + \midrule + \t{pkg\_pretend}, \t{pkg\_setup}, \t{pkg\_info}, \t{pkg\_nofetch} & None = (ebuilds can rely only on the packages in the system set) \\ + \t{src\_unpack}, \t{src\_prepare}, \t{src\_configure}, \t{src\_compile= }, \t{src\_test}, \t{src\_install} & \t{DEPEND} \\ + \t{pkg\_preinst}, \t{pkg\_postinst}, \t{pkg\_prerm}, \t{pkg\_postrm}, = \t{pkg\_config} & \t{RDEPEND} \\ + \bottomrule + \end{tabular} +\end{centertable} + +Table~\ref{tab:phase-function-dependency-classes} lists dependencies which= must be satisfied before a particular phase function is executed. + In addition, \t{SRC\_URI}, \t{HOMEPAGE}, \t{PROVIDE}, \t{RESTRICT}, \t{PRO= PERTIES}, \t{LICENSE} and \t{REQUIRED\_USE} use dependency-style specifications to specify their val= ues. =20 --=20 1.7.5.3 --MP_/+5BY6.jwkzLv4dkJ79eXeOT-- --Sig_/XH+PzyxsBHPHTnMzE113Zcs Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iJwEAQEIAAYFAk31CvQACgkQfXuS5UK5QB2I5wP/WiGhCmyi+65Jk16AVuFcl7iQ diWgCaff6Ak6aLmiQia//CTY2CtQHQCkeAkH8iVy/CR+blknlQIA6NqIiV8ZImVa ftSK9FPHJvPRwSPymxcXpxssadSbI59ENDwwLvO/Y7Az9lV8Wq97Q9r5R3R9SI+N 0bSX+4eReTiVESoU7K0= =rQpn -----END PGP SIGNATURE----- --Sig_/XH+PzyxsBHPHTnMzE113Zcs--