| 1 |
On Tue, 2002-03-12 at 00:42, Ian Smith wrote: |
| 2 |
> Defresne Sylvain wrote: |
| 3 |
> |
| 4 |
> > Then export CONFIG_PROTECT_MASK="/etc/init.d" and then /etc/init.d will be |
| 5 |
> > excluded from config file protection ! If you like it, you can add it to |
| 6 |
> > /etc/make.conf ... |
| 7 |
> > |
| 8 |
> > Bye |
| 9 |
> > |
| 10 |
> |
| 11 |
> Ah you've answered my post anyway! Is this documented anywhere? I |
| 12 |
> think at least a blank entry in /etc/make.globals would be useful . . . |
| 13 |
|
| 14 |
nosferatu init.d # emerge |
| 15 |
|
| 16 |
* Regenerating GNU info directory index... |
| 17 |
* Processed 73 info files. |
| 18 |
* IMPORTANT: 14 config files in /etc need updating. |
| 19 |
* Type emerge --help config to learn how to update config files. |
| 20 |
|
| 21 |
nosferatu init.d # emerge --help config |
| 22 |
|
| 23 |
Config file management support (preliminary) |
| 24 |
|
| 25 |
Portage has a special feature called "config file protection". The |
| 26 |
purpose of |
| 27 |
this feature is to prevent new package installs from clobbering existig |
| 28 |
configuration files. By default, config file protection is turned on |
| 29 |
for /etc |
| 30 |
and the KDE configuration dirs; more may be added in the future. |
| 31 |
|
| 32 |
When Portage installs a file into a protected directory tree like /etc, |
| 33 |
any |
| 34 |
existing files will not be overwritten. If a file of the same name |
| 35 |
already |
| 36 |
exists, Portage will change the name of the to-be- installed file from |
| 37 |
'foo' to |
| 38 |
'._cfg0000_foo'. If '._cfg0000_foo' already exists, this name becomes |
| 39 |
'._cfg0001_foo', etc. In this way, existing files are not overwritten, |
| 40 |
allowing the administrator to manually merge the new config files and |
| 41 |
avoid any |
| 42 |
unexpected changes. |
| 43 |
|
| 44 |
In addition to protecting overwritten files, Portage will not delete any |
| 45 |
files |
| 46 |
from a protected directory when a package is unmerged. While this may |
| 47 |
be a |
| 48 |
little bit untidy, it does prevent potentially valuable config files |
| 49 |
from being |
| 50 |
deleted, which is of paramount importance. |
| 51 |
|
| 52 |
Protected directories are set using the CONFIG_PROTECT variable, |
| 53 |
normally |
| 54 |
defined in /etc/make.globals. Directory exceptions to the |
| 55 |
CONFIG_PROTECTed |
| 56 |
directories can be specified using the CONFIG_PROTECT_MASK variable. To |
| 57 |
find |
| 58 |
files that need to be updated in /etc, type: |
| 59 |
|
| 60 |
# find /etc -iname '._cfg????_*' |
| 61 |
|
| 62 |
You can disable this feature by setting CONFIG_PROTECT="" in |
| 63 |
/etc/make.conf. |
| 64 |
Then, Portage will mercilessly auto-update your config files. |
| 65 |
Alternatively, |
| 66 |
you can leave Config File Protection on but tell Portage that it can |
| 67 |
overwrite |
| 68 |
files in certain specific /etc subdirectories. For example, if you |
| 69 |
wanted |
| 70 |
Portage to automatically update your rc scripts and your wget |
| 71 |
configuration, |
| 72 |
but didn't want any other changes made without your explicit approval, |
| 73 |
you'd |
| 74 |
add this to /etc/make.conf: |
| 75 |
|
| 76 |
CONFIG_PROTECT_MASK="/etc/wget /etc/rc.d" |
| 77 |
|
| 78 |
*Look Here ^^ |
| 79 |
============== |
| 80 |
|
| 81 |
> |
| 82 |
> -- |
| 83 |
> ---------------------------------------------------------------------------- |
| 84 |
> Ian Smith |
| 85 |
> ---------------------------------------------------------------------------- |
| 86 |
> |
| 87 |
> _______________________________________________ |
| 88 |
> gentoo-dev mailing list |
| 89 |
> gentoo-dev@g.o |
| 90 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 91 |
-- |
| 92 |
|
| 93 |
Martin Schlemmer |
| 94 |
Gentoo Linux Developer, Desktop Team Developer |
| 95 |
Cape Town, South Africa |
Archives