1 |
On Mon, 6 Jan 2014 23:50:02 +0200, Gevisz wrote: |
2 |
|
3 |
> On Sun, 5 Jan 2014 10:16:20 +0000 |
4 |
> Neil Bothwick <neil@××××××××××.uk> wrote: |
5 |
|
6 |
> > CONFIG_PROTECT_MASK is a make.conf setting, read that man page. It |
7 |
> > means your config files are overwritten at install time, way be for |
8 |
> > you run dispatch-conf or one of its friends. |
9 |
> |
10 |
> The man page for make.conf actually refers to the CONFIGURATION FILES |
11 |
> section of emerge man page. There, indeed, everything explained very |
12 |
> clearly and in details. However, it does not work so for my system. |
13 |
|
14 |
> |
15 |
> Thus, I have the following settings |
16 |
> |
17 |
> $ echo $CONFIG_PROTECT |
18 |
> /usr/share/gnupg/qualified.txt |
19 |
|
20 |
CONFIG_PROTECT is not a global environment variable. Also, variables like |
21 |
this are not only set in make.conf but in profiles and even on |
22 |
the command line. Read man portage for more detail. |
23 |
|
24 |
The correct way to see what settings are in place is to run emerge --info |
25 |
|
26 |
emerge --info | grep CONFIG_PROTECT |
27 |
|
28 |
> And this, in my view, contradicts with the following statement from |
29 |
> emerge man pages: "Protected directories are set using the |
30 |
> CONFIG_PROTECT variable", as in my case /etc have not been set in |
31 |
> my CONFIG_PROTECT variable. |
32 |
|
33 |
See above. /etc is protected in the base profile, inherited by all others. |
34 |
|
35 |
|
36 |
-- |
37 |
Neil Bothwick |
38 |
|
39 |
"Logic will get you from A to B. Imagination will take you everywhere." |
40 |
(Albert Einstein) |