diff options
| author |   Mark Loeser <halcy0n@gentoo.org> | 2006-02-27 18:47:36 +0000 |
|---|---|---|
| committer | Mark Loeser <halcy0n@gentoo.org> | 2006-02-27 18:47:36 +0000 |
| commit | 6e10960ec77f77952c14c0b89f7b875b52cb828c (patch) | |
| tree | 54a4b731e8c00356a1b8332cf83a459e0ff959b4 | |
| parent | Fix markup in one or two places for *text*. (diff) | |
| download | devmanual-6e10960ec77f77952c14c0b89f7b875b52cb828c.tar.gz devmanual-6e10960ec77f77952c14c0b89f7b875b52cb828c.tar.bz2 devmanual-6e10960ec77f77952c14c0b89f7b875b52cb828c.zip | |
<i> -> <e>
git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/devmanual/trunk@9 176d3534-300d-0410-8db8-84e73ed771c3
| -rw-r--r-- | general-concepts/dependencies/text.xml | 10 | ||||
| -rw-r--r-- | general-concepts/digest-and-manifest/text.xml | 4 | ||||
| -rw-r--r-- | general-concepts/herds-and-projects/text.xml | 6 | ||||
| -rw-r--r-- | general-concepts/install-destinations/text.xml | 2 |
4 files changed, 11 insertions, 11 deletions
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml index 70d5b90..da5153d 100644 --- a/general-concepts/dependencies/text.xml +++ b/general-concepts/dependencies/text.xml @@ -41,8 +41,8 @@ in <c>DEPEND</c>. </p> <p> -Items which are in <c>RDEPEND</c> but not <c>DEPEND</c> could <i>in theory</i> be merged -<i>after</i> the target package. Portage does not currently do this. +Items which are in <c>RDEPEND</c> but not <c>DEPEND</c> could <e>in theory</e> be merged +<e>after</e> the target package. Portage does not currently do this. </p> </body> @@ -53,7 +53,7 @@ Items which are in <c>RDEPEND</c> but not <c>DEPEND</c> could <i>in theory</i> b <body> <p> -The <c>PDEPEND</c> variable specifies dependencies which must be merged <i>after</i> the +The <c>PDEPEND</c> variable specifies dependencies which must be merged <e>after</e> the package. This is sometimes used for plugins which have a dependency upon the package being merged. Generally <c>PDEPEND</c> should be avoided in favour of <c>RDEPEND</c> except where this will create circular dependency chains. @@ -207,7 +207,7 @@ RDEPEND="!app-misc/foo" </codesample> <p> -Note that blockers are usually <i>runtime</i> rather than buildtime. +Note that blockers are usually <e>runtime</e> rather than buildtime. </p> <p> @@ -256,7 +256,7 @@ DEPEND="perl? ( dev-lang/perl ) <p> It is also possible to depend upon a certain package if a given <c>USE</c> flag is -<i>not</i> set: +<e>not</e> set: </p> <codesample language="ebuild"> diff --git a/general-concepts/digest-and-manifest/text.xml b/general-concepts/digest-and-manifest/text.xml index abcce82..541d622 100644 --- a/general-concepts/digest-and-manifest/text.xml +++ b/general-concepts/digest-and-manifest/text.xml @@ -23,8 +23,8 @@ to catch any changed source files. </p> <p> -When generating digests, it is necessary to include <i>all</i> of the files which -<i>could</i> be downloaded (<c>SRC_URI</c> can contain conditional entries). Portage +When generating digests, it is necessary to include <e>all</e> of the files which +<e>could</e> be downloaded (<c>SRC_URI</c> can contain conditional entries). Portage will do this automatically if <c>cvs</c> is included in <c>FEATURES</c>. </p> diff --git a/general-concepts/herds-and-projects/text.xml b/general-concepts/herds-and-projects/text.xml index c70754b..c6f9811 100644 --- a/general-concepts/herds-and-projects/text.xml +++ b/general-concepts/herds-and-projects/text.xml @@ -6,7 +6,7 @@ <body> <p> -A <i>herd</i> is a collection of developers who maintain a collection of related +A <e>herd</e> is a collection of developers who maintain a collection of related packages. A herd has an associated email address which can be used for bugzilla assignments. This email address is <b>not</b> always <c>herdname@gentoo.org</c> -- for example, because of the way Gentoo's email aliases are set up, the <c>cron</c> herd @@ -14,14 +14,14 @@ use <c>cron-bugs@gentoo.org</c> (aliases cannot match system usernames). </p> <p> -A <i>project</i> is a group formed for handling a particular general area. A project +A <e>project</e> is a group formed for handling a particular general area. A project may have herds associated with it. </p> <p> Sometimes herd and project names overlap -- for example, the <c>sparc</c> project has an associated <c>sparc</c> herd which maintains sparc-specific packages (such -as the <c>silo</c> bootloader). This is <i>not</i> always the case. +as the <c>silo</c> bootloader). This is <e>not</e> always the case. </p> <p> diff --git a/general-concepts/install-destinations/text.xml b/general-concepts/install-destinations/text.xml index dbe0492..ff51cdf 100644 --- a/general-concepts/install-destinations/text.xml +++ b/general-concepts/install-destinations/text.xml @@ -7,7 +7,7 @@ <p> When an ebuild runs the <c>src_install</c> phase, it installs an image of the -package in question from <c>${S}</c> into <c>${D}</c>. Ebuilds must <i>not</i> attempt to +package in question from <c>${S}</c> into <c>${D}</c>. Ebuilds must <e>not</e> attempt to perform any operation upon the live filesystem at this stage -- this will break binaries, and will (often) cause a sandbox violation notice. </p> |