1 |
Graham Murray wrote: |
2 |
> Benno Schulenberg <benno.schulenberg@×××××.com> writes: |
3 |
> > /etc is in CONFIG_PROTECT by default. The point is, when a |
4 |
> > file doesn't exist yet, Portage will simply install it. The |
5 |
> > config protection mechanism works only for existing files. |
6 |
> > There's no way to tell Portage that I want to be alerted of |
7 |
> > _new config files too. |
8 |
> |
9 |
> Which is maybe something worth raising an enhancement bug on, |
10 |
|
11 |
Done: https://bugs.gentoo.org/show_bug.cgi?id=177560 |
12 |
|
13 |
Quote: |
14 |
" When a file under CONFIG_PROTECT doesn't exist yet, Portage |
15 |
simply installs it. It would be nice to have an option (say |
16 |
--protectforreal) that makes emerge create a .cfg_0000_* file also |
17 |
when the destination file does not exist yet in the CONFIG_PROTECT |
18 |
area. When first installing a system, one wouldn't want to use |
19 |
this option, but once a system is fully installed and stable, I |
20 |
wish to know about every change and addition in /etc." |
21 |
|
22 |
Benno |
23 |
-- |
24 |
gentoo-user@g.o mailing list |