diff options
| -rw-r--r-- | general-concepts/dependencies/text.xml | 17 | ||||
| -rw-r--r-- | profiles/packages/text.xml | 2 | ||||
| -rw-r--r-- | tools-reference/sed/text.xml | 3 |
3 files changed, 13 insertions, 9 deletions
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml index e43390c..2f10380 100644 --- a/general-concepts/dependencies/text.xml +++ b/general-concepts/dependencies/text.xml @@ -73,21 +73,24 @@ where this will create circular dependency chains. <p> All packages have an implicit compile-time and runtime dependency upon the -entire <c>system</c> target. It is therefore not necessary, nor advisable, to +entire <c>@system</c> set. It is therefore not necessary, nor +advisable, to specify dependencies upon toolchain packages like <c>gcc</c>, <c>libc</c> and so on, except where specific versions or packages (for example, <c>glibc</c> over <c>uclibc</c>) are required. Note that this rule also needs consideration for packages like <c>flex</c>, <c>zlib</c> and <c>libtool</c>, which aren't in -the <c>system</c> target for every profile. For example, the embedded profile -doesn't have <c>zlib</c> in <c>system</c> target, the <c>libtool</c> ABI might +the <c>@system</c> set for every profile. For example, the embedded +profile doesn't have <c>zlib</c> in <c>@system</c>, the <c>libtool</c> +ABI might change and break building order and <c>flex</c> might get removed from the -<c>system</c> target in future. +<c>@system</c> set in future. </p> <p> -However, packages which are included in the <c>system</c> target, or are -dependencies of <c>system</c> target packages, should generally include a complete -dependency list (excluding bootstrap packages). This makes <c>emerge -e system</c> +However, packages which are included in the <c>@system</c> set, or are +dependencies of <c>@system</c> set packages, should generally include +a complete dependency list (excluding bootstrap packages). This makes +<c>emerge -e @system</c> possible when installing from a stage 1 or stage 2 tarball. </p> diff --git a/profiles/packages/text.xml b/profiles/packages/text.xml index b8215f7..13f98ab 100644 --- a/profiles/packages/text.xml +++ b/profiles/packages/text.xml @@ -6,7 +6,7 @@ <p> The <c>packages</c> file in <c>profiles/</c> controls the packages pulled in by the -<c>system</c> target. The <c>base/packages</c> file must not be modified without +<c>@system</c> set. The <c>base/packages</c> file must not be modified without discussion on the <c>gentoo-dev</c> list; subprofile overrides are up to the relevant arch teams. </p> diff --git a/tools-reference/sed/text.xml b/tools-reference/sed/text.xml index 02c8c32..3f7a455 100644 --- a/tools-reference/sed/text.xml +++ b/tools-reference/sed/text.xml @@ -62,7 +62,8 @@ A summary of the more common ways of using <c>sed</c> and a description of commonly used address and token patterns follows. Note that some of these constructs are specific to <c>GNU sed 4</c> <d/> on non-GNU userland archs, the <c>sed</c> command must be aliased to GNU sed. Also note that <c>GNU sed 4</c> is -guaranteed to be installed as part of <c>system</c>. This was not always the case, +guaranteed to be installed as part of <c>@system</c>. This was not +always the case, which is why some packages, particularly those which use <c>sed -i</c>, have <c>DEPEND</c> s upon <c>>=sys-apps/sed-4</c>. </p> |