| 1 |
Hi! |
| 2 |
|
| 3 |
On Mon, 2002-03-11 at 11:48, Yannick Koehler wrote: |
| 4 |
> |
| 5 |
> Guys, |
| 6 |
> |
| 7 |
> not sure for anyone else but is init.d really need to be protected? I |
| 8 |
> mean does someone really change files in that directory (other than |
| 9 |
> adding or removing)? |
| 10 |
|
| 11 |
I suggest that you review 'emerge --help config' |
| 12 |
|
| 13 |
Summary: |
| 14 |
|
| 15 |
Protected directories are set with CONFIG_PROTECT= in /etc/make.conf |
| 16 |
(global setting is in /etc/make.globals). |
| 17 |
|
| 18 |
To override for a particular directory or subdirectory use |
| 19 |
CONFIG_PROTECT_MASK= |
| 20 |
|
| 21 |
For example, |
| 22 |
|
| 23 |
CONFIG_PROTECT="/etc" |
| 24 |
|
| 25 |
to protect everything under /etc from getting automagically updated. |
| 26 |
|
| 27 |
CONFIG_PROTECT_MASK="/etc/init.d" |
| 28 |
|
| 29 |
if you want to allow stuff under /etc/init.d to be updated without |
| 30 |
review. |
| 31 |
|
| 32 |
|
| 33 |
Essentially all the functionality that you mention already exists. |
| 34 |
Also, as has already been mentioned, etc-update is your friend. |
| 35 |
|
| 36 |
Hope that helps, |
| 37 |
|
| 38 |
tod |
Archives