aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUlrich Müller <ulm@gentoo.org>2022-06-05 23:03:45 +0200
committerUlrich Müller <ulm@gentoo.org>2022-06-05 23:03:45 +0200
commitdb7c43d1218802367ebb3f0ae6bf1903de578a43 (patch)
tree609c20a186740d544eda9dad642f9a2dc9a09113 /general-concepts
parentgeneral-concepts/config-protect: Add example for env.d (diff)
downloaddevmanual-db7c43d1218802367ebb3f0ae6bf1903de578a43.tar.gz
devmanual-db7c43d1218802367ebb3f0ae6bf1903de578a43.tar.bz2
devmanual-db7c43d1218802367ebb3f0ae6bf1903de578a43.zip
general-concepts/config-protect: Whitespace
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'general-concepts')
-rw-r--r--general-concepts/config-protect/text.xml29
1 files changed, 15 insertions, 14 deletions
diff --git a/general-concepts/config-protect/text.xml b/general-concepts/config-protect/text.xml
index cca1457..c103108 100644
--- a/general-concepts/config-protect/text.xml
+++ b/general-concepts/config-protect/text.xml
@@ -2,28 +2,29 @@
<guide self="general-concepts/config-protect/">
<chapter>
<title>Configuration File Protection</title>
-
<body>
+
<p>
- Portage includes a system for configuration file protection which means ebuilds
- don't have to worry about accidentally clobbering files in <c>/etc</c>. This is
- known as 'protection', and it is controlled by the <c>CONFIG_PROTECT</c> and
- <c>CONFIG_PROTECT_MASK</c> variables.
+Portage includes a system for configuration file protection which means ebuilds
+don't have to worry about accidentally clobbering files in <c>/etc</c>. This is
+known as 'protection', and it is controlled by the <c>CONFIG_PROTECT</c> and
+<c>CONFIG_PROTECT_MASK</c> variables.
</p>
<p>
- Any directory which is listed in <c>CONFIG_PROTECT</c> (and any subdirectories
- thereof), except for any which are listed in <c>CONFIG_PROTECT_MASK</c> (and
- subdirectories) are automatically 'protected' by Portage when copying an image
- from <c>DESTDIR</c> to <c>ROOT</c>. Rather than installing protected files directly,
- Portage will install them as <c>._cfg0000_filename</c>. These can then be processed
- by the <c>etc-update</c> or <c>dispatch-conf</c> files at the user's discretion.
+Any directory which is listed in <c>CONFIG_PROTECT</c> (and any subdirectories
+thereof), except for any which are listed in <c>CONFIG_PROTECT_MASK</c> (and
+subdirectories) are automatically 'protected' by Portage when copying an image
+from <c>DESTDIR</c> to <c>ROOT</c>. Rather than installing protected files
+directly, Portage will install them as <c>._cfg0000_filename</c>. These can
+then be processed by the <c>etc-update</c> or <c>dispatch-conf</c> files at
+the user's discretion.
</p>
<p>
- Packages must <b>not</b> attempt to override this system via <c>pkg_postinst</c> or
- similar. If you need a file renamed, removed or changed in a particular way, you
- should display a message informing the user.
+Packages must <b>not</b> attempt to override this system via <c>pkg_postinst</c>
+or similar. If you need a file renamed, removed or changed in a particular way,
+you should display a message informing the user.
</p>
<p>