aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2021-03-20 15:00:59 +0000
committerUlrich Müller <ulm@gentoo.org>2021-03-21 07:06:12 +0100
commit0b0aeb084ae51e2df6622b639dbc4fcaede3f302 (patch)
treef8b52979aaeffe52f2edfd17b83b0dd2e9f76362 /appendices
parentebuild-writing/functions/*: fix non-standard brace style in example (diff)
downloaddevmanual-0b0aeb084ae51e2df6622b639dbc4fcaede3f302.tar.gz
devmanual-0b0aeb084ae51e2df6622b639dbc4fcaede3f302.tar.bz2
devmanual-0b0aeb084ae51e2df6622b639dbc4fcaede3f302.zip
*/*: consistent 'Portage' casing
Signed-off-by: Sam James <sam@gentoo.org> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'appendices')
-rw-r--r--appendices/common-problems/text.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/appendices/common-problems/text.xml b/appendices/common-problems/text.xml
index a2af22a..4fcdda4 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -15,9 +15,9 @@ and QA notices.
<body>
<p>
-The <c>ebuild.sh</c> part of portage includes a number of checks for common
+The <c>ebuild.sh</c> part of Portage includes a number of checks for common
problems. These can result in a 'QA Notice' message being displayed. You must
-not rely upon portage always generating these messages <d/> they are not a
+not rely upon Portage always generating these messages <d/> they are not a
substitute for proper testing and QA by developers.
</p>
@@ -126,7 +126,7 @@ inheritance occurring. Most commonly:
<ul>
<li>
- When unmerging a package which was installed using an old portage version that
+ When unmerging a package which was installed using an old Portage version that
did not record inheritance.
</li>
<li>
@@ -134,7 +134,7 @@ inheritance occurring. Most commonly:
link="::general-concepts/overlay/#Overlay and Eclasses"/>.
</li>
<li>
- When working with a stale portage cache.
+ When working with a stale Portage cache.
</li>
</ul>
@@ -150,7 +150,7 @@ from vapier:
TEXTREL's ... binary files which contain text relocations ... see
'prepstrip' for a full description unsafe files ... basically files that
are setid and writable by Other users i've added the following QA checks to
-portage HEAD (no idea when they'll hit a release): Insecure RUNPATHs ...
+Portage HEAD (no idea when they'll hit a release): Insecure RUNPATHs ...
binary files which have RUNPATH's encoded in them which are in +t
directories Executable stacks ... binary files whose stack is marked with
+x ... will bomb on amd64 for example