Dependencies

Dependencies -

Automatic dependency resolution is one of the most useful features provided by emerge.

+Dependency types + + CHOST vs CBUILD @@ -41,9 +44,9 @@ of dependencies are merged.

+ -

+ Build Dependencies @@ -67,9 +70,9 @@ In earlier EAPIs, all build dependencies are placed in DEPEND.

+ -

+ Runtime Dependencies @@ -91,9 +94,9 @@ Items which are in RDEPEND but not DEPEND could in theory b

+ -

+ Post Dependencies @@ -105,39 +108,13 @@ while in general case RDEPEND should be used instead.

-Implicit System Dependency - +Dependency Syntax -

-All packages have an implicit compile-time and runtime dependency upon the -entire @system set. It is therefore not necessary, nor -advisable, to -specify dependencies upon toolchain packages like gcc, libc and -so on, except where specific versions or packages (for example, glibc -over uclibc) are required. Note that this rule also needs consideration -for packages like flex, zlib and libtool, which aren't in -the @system set for every profile. For example, the embedded -profile doesn't have zlib in @system, the libtool -ABI might -change and break building order and flex might get removed from the -@system set in future. -

- -

-However, packages which are included in the @system set, or are -dependencies of @system set packages, should generally include -a complete dependency list (excluding bootstrap packages). This makes -emerge -e @system -possible when installing from a stage 1 or stage 2 tarball. -

- - -

- -

+ Basic Dependency Syntax @@ -159,9 +136,9 @@ When specifying names, the category part should be treated as mandatory.

+ -

+ Version Dependencies @@ -179,7 +156,7 @@ This states that at least version 0.9.7d of openssl is required.

- + Version Specifiers @@ -222,9 +199,9 @@ Available version specifiers are: - + - + Ranged Dependencies @@ -244,9 +221,9 @@ asterisk. Also note that when selecting all versions in a specific

- + - + Blockers @@ -343,10 +320,10 @@ newer package that caused the issues.

+ -

+ SLOT Dependencies @@ -370,7 +347,7 @@ DEPEND="qt3? ( ~x11-libs/qt-3.3.8:3 ) - + Slot Operators @@ -407,10 +384,10 @@ RDEPEND="media-libs/cogl:1.0= + -

+ USE-Conditional Dependencies @@ -464,9 +441,9 @@ DEPEND="!build? ( -

+ -

+ Any of Many Dependencies @@ -487,7 +464,7 @@ DEPEND="baz? ( || ( app-misc/foo app-misc/bar ) )" - + Any of Many Versus USE @@ -509,10 +486,10 @@ flag is not necessary if and only if all of the following hold: + -

+ Built with USE Dependencies @@ -567,7 +544,7 @@ There are also shortcuts for conditional situations: - + Use dependency defaults @@ -592,9 +569,38 @@ DEPEND=" +

+Implicit System Dependency + + +

+All packages have an implicit compile-time and runtime dependency upon the +entire @system set. It is therefore not necessary, nor advisable, to +specify dependencies upon toolchain packages like gcc, libc and +so on, except where specific versions or packages (for example, glibc +over uclibc) are required. Note that this rule also needs consideration +for packages like flex, zlib and libtool, which aren't in +the @system set for every profile. For example, the embedded profile +doesn't have zlib in @system, the libtool ABI might +change and break building order and flex might get removed from the +@system set in future. +

+ +

+However, packages which are included in the @system set, or are +dependencies of @system set packages, should generally include +a complete dependency list (excluding bootstrap packages). This makes +emerge -e @system possible when installing from a stage 1 or stage 2 +tarball. +

+ + +

Test Dependencies