| 1 |
Simon Stelling wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> (If you are receiving this mail a second time, sorry, I had some |
| 5 |
> problems with my mail setup. Please answer to this thread) |
| 6 |
> |
| 7 |
> When unmerging apache, i saw various lines like |
| 8 |
> |
| 9 |
> --- cfgpro /etc/init.d/apache |
| 10 |
> |
| 11 |
> I really wonder why the configuration files stay. This behaviour IMHO |
| 12 |
> leds to unneeded orphaned files and is certainly not what the end user |
| 13 |
> wants, so I'd like to know if there is a reason for leaving it as is. |
| 14 |
> I'm nearly sure I missed something. |
| 15 |
> |
| 16 |
> Regards, |
| 17 |
> |
| 18 |
|
| 19 |
They stay because of CONFIG_PROTECT, the make.conf manpage has details |
| 20 |
on how to use it. Basically people want to merge config file changes |
| 21 |
manually so they protect certain directories from portage's hands. see |
| 22 |
also emerge --help config. |
| 23 |
-- |
| 24 |
gentoo-portage-dev@g.o mailing list |
Archives