1 |
commit: db7c43d1218802367ebb3f0ae6bf1903de578a43 |
2 |
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
3 |
AuthorDate: Sun Jun 5 21:03:45 2022 +0000 |
4 |
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
5 |
CommitDate: Sun Jun 5 21:03:45 2022 +0000 |
6 |
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=db7c43d1 |
7 |
|
8 |
general-concepts/config-protect: Whitespace |
9 |
|
10 |
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> |
11 |
|
12 |
general-concepts/config-protect/text.xml | 29 +++++++++++++++-------------- |
13 |
1 file changed, 15 insertions(+), 14 deletions(-) |
14 |
|
15 |
diff --git a/general-concepts/config-protect/text.xml b/general-concepts/config-protect/text.xml |
16 |
index cca1457..c103108 100644 |
17 |
--- a/general-concepts/config-protect/text.xml |
18 |
+++ b/general-concepts/config-protect/text.xml |
19 |
@@ -2,28 +2,29 @@ |
20 |
<guide self="general-concepts/config-protect/"> |
21 |
<chapter> |
22 |
<title>Configuration File Protection</title> |
23 |
- |
24 |
<body> |
25 |
+ |
26 |
<p> |
27 |
- Portage includes a system for configuration file protection which means ebuilds |
28 |
- don't have to worry about accidentally clobbering files in <c>/etc</c>. This is |
29 |
- known as 'protection', and it is controlled by the <c>CONFIG_PROTECT</c> and |
30 |
- <c>CONFIG_PROTECT_MASK</c> variables. |
31 |
+Portage includes a system for configuration file protection which means ebuilds |
32 |
+don't have to worry about accidentally clobbering files in <c>/etc</c>. This is |
33 |
+known as 'protection', and it is controlled by the <c>CONFIG_PROTECT</c> and |
34 |
+<c>CONFIG_PROTECT_MASK</c> variables. |
35 |
</p> |
36 |
|
37 |
<p> |
38 |
- Any directory which is listed in <c>CONFIG_PROTECT</c> (and any subdirectories |
39 |
- thereof), except for any which are listed in <c>CONFIG_PROTECT_MASK</c> (and |
40 |
- subdirectories) are automatically 'protected' by Portage when copying an image |
41 |
- from <c>DESTDIR</c> to <c>ROOT</c>. Rather than installing protected files directly, |
42 |
- Portage will install them as <c>._cfg0000_filename</c>. These can then be processed |
43 |
- by the <c>etc-update</c> or <c>dispatch-conf</c> files at the user's discretion. |
44 |
+Any directory which is listed in <c>CONFIG_PROTECT</c> (and any subdirectories |
45 |
+thereof), except for any which are listed in <c>CONFIG_PROTECT_MASK</c> (and |
46 |
+subdirectories) are automatically 'protected' by Portage when copying an image |
47 |
+from <c>DESTDIR</c> to <c>ROOT</c>. Rather than installing protected files |
48 |
+directly, Portage will install them as <c>._cfg0000_filename</c>. These can |
49 |
+then be processed by the <c>etc-update</c> or <c>dispatch-conf</c> files at |
50 |
+the user's discretion. |
51 |
</p> |
52 |
|
53 |
<p> |
54 |
- Packages must <b>not</b> attempt to override this system via <c>pkg_postinst</c> or |
55 |
- similar. If you need a file renamed, removed or changed in a particular way, you |
56 |
- should display a message informing the user. |
57 |
+Packages must <b>not</b> attempt to override this system via <c>pkg_postinst</c> |
58 |
+or similar. If you need a file renamed, removed or changed in a particular way, |
59 |
+you should display a message informing the user. |
60 |
</p> |
61 |
|
62 |
<p> |