We can basically assume PM merges either DEPEND or RDEPEND to that point
(depending on whether we're merging source ebuild or binary package).
---
dependencies.tex | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/dependencies.tex b/dependencies.tex
index abcb820..557660a 100644
--- a/dependencies.tex
+++ b/dependencies.tex
@@ -10,7 +10,8 @@
\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{pkg\_pretend}, \t{pkg\_info}, \t{pkg\_nofetch} & None (ebuilds can rely only on the packages in the system set) \\
+ \t{pkg\_setup} & packages common to \t{DEPEND} and \t{RDEPEND} (but see below) \\
\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{RDEPEND} (unless the particular dependency results in a circular dependency, in which case it may be installed later) \\
\t{pkg\_config} & \t{RDEPEND}, \t{PDEPEND} \\
--
1.7.6
|
