1 |
Peter Campion-Bye wrote: |
2 |
|
3 |
>Hi, |
4 |
>Apologies if I've misunderstood the use of CONFIG_PROTECT, but I think |
5 |
>I've found a hole in it. As I have lots of stuff under |
6 |
>/var/www/localhost/htdocs which contains configuration files mixed in with |
7 |
>the code ( phpmyadmin, phpldapadmin, phpwiki, squirrelmail, gallery etc ) |
8 |
>I have put the path /var/www/localhost/htdocs into CONFIG_PROTECT in |
9 |
>make.conf. When one of these packages is upgraded this seems to work fine. |
10 |
>Last night, after upgrading PHP to 4.4.0 my wiki was broken. I thought a |
11 |
>good place to start would be to re-emerge phpwiki, so I did. During the |
12 |
>emerge it flashed up a message about this being a package that it couldn't |
13 |
>upgrade, so it would be unmerged it first. It appears that this bypassed |
14 |
>the CONFIG_PROTECT mechanism, as when the new files were installed the |
15 |
>original had been removed, so no ._cfg0000_ files were created for the |
16 |
>changed files. |
17 |
>Having no recent backup (lesson learned!) I had to recreate the phpwiki |
18 |
>config, which is a non-trivial job. |
19 |
>So the question is, how can config files be protected in this kind of |
20 |
>situation (other than backing them up) - is there another mechanism to |
21 |
>protect files from being overwritten, and how many packages are likely to |
22 |
>do an unmerge before re-emerging, and is there ay way of knowing? I |
23 |
>believe the default behaviour on umnerging a package is to leave its |
24 |
>configuration files in place, this doesn't seem to apply to the web apps |
25 |
> |
26 |
> |
27 |
|
28 |
Ouch. Do you by chance have CONFIG_PROTECT_MASK set also? Check |
29 |
"emerge --info".. |
30 |
|
31 |
-Richard |
32 |
|
33 |
-- |
34 |
gentoo-user@g.o mailing list |