1 |
Hello all |
2 |
|
3 |
"To protect or not to protect..." |
4 |
|
5 |
emerge tool overwrite files in CONFIG_PROTECT if ROOT != '/' |
6 |
|
7 |
for example: |
8 |
CONFIG_PROTECT="/etc /opt/gentoos/hostname/root/etc" |
9 |
ROOT="/opt/gentoos/hostname/root/" |
10 |
emerge something |
11 |
overwrite files in /opt/gentoos/hostname/root/etc |
12 |
|
13 |
I found the comments of Nicholas Jones in bug |
14 |
http://bugs.gentoo.org/show_bug.cgi?id=52415 |
15 |
>> Portage makes the assumption that if you're installing |
16 |
>> into a new root, then you're building a system and |
17 |
>> shouldn't bother with config protection. It's not |
18 |
>> documented either way, so it's undefined behavior. |
19 |
|
20 |
But if I really want to overwrite those files |
21 |
I can do it by |
22 |
CONFIG_PROTECT="-*" |
23 |
ROOT="/opt/gentoos/hostname/root/" |
24 |
emerge something |
25 |
|
26 |
I can't chroot to /opt/gentoos/hostname/root and emerge there, |
27 |
because it is cross compilation and I can't protect those files |
28 |
in any way now. |
29 |
|
30 |
May be protect *all* files in CONFIG_PROTECT |
31 |
even if ROOT != '/' |
32 |
This behavior can be easy override by CONFIG_PROTECT="-*" |
33 |
in command line if needed. |
34 |
|
35 |
Thanks. |
36 |
|
37 |
|
38 |
-- |
39 |
Vitaly Ivanov |
40 |
email: va@××××.ru |
41 |
icq uin: 15918498 |
42 |
-- |
43 |
gentoo-dev@g.o mailing list |