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