| 1 |
On Monday 07 May 2007, Benno Schulenberg wrote: |
| 2 |
> Graham Murray wrote: |
| 3 |
> > Benno Schulenberg <benno.schulenberg@×××××.com> writes: |
| 4 |
> > > /etc is in CONFIG_PROTECT by default. The point is, when a |
| 5 |
> > > file doesn't exist yet, Portage will simply install it. The |
| 6 |
> > > config protection mechanism works only for existing files. |
| 7 |
> > > There's no way to tell Portage that I want to be alerted of |
| 8 |
> > > _new config files too. |
| 9 |
> > |
| 10 |
> > Which is maybe something worth raising an enhancement bug on, |
| 11 |
> |
| 12 |
> Done: https://bugs.gentoo.org/show_bug.cgi?id=177560 |
| 13 |
> |
| 14 |
> Quote: |
| 15 |
> " When a file under CONFIG_PROTECT doesn't exist yet, Portage |
| 16 |
> simply installs it. It would be nice to have an option (say |
| 17 |
> --protectforreal) that makes emerge create a .cfg_0000_* file also |
| 18 |
> when the destination file does not exist yet in the CONFIG_PROTECT |
| 19 |
> area. When first installing a system, one wouldn't want to use |
| 20 |
> this option, but once a system is fully installed and stable, I |
| 21 |
> wish to know about every change and addition in /etc." |
| 22 |
> |
| 23 |
> Benno |
| 24 |
|
| 25 |
It's an original idea, but the first comment to the report isn't |
| 26 |
encouraging... |
| 27 |
|
| 28 |
I would add in a comment to the bug a pointer to the mailing list |
| 29 |
archive, but i can't find one, maybe reading this thread would be more |
| 30 |
convincing. |
| 31 |
|
| 32 |
Ciao |
| 33 |
Francesco |
| 34 |
-- |
| 35 |
Linux Version 2.6.21-gentoo, Compiled #1 PREEMPT Mon Apr 30 21:45:34 |
| 36 |
CEST 2007 |
| 37 |
One 2.2GHz AMD Athlon 64 Processor, 2GB RAM, 4408.86 Bogomips Total |
| 38 |
aemaeth |
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives