When doing an "emerge vmware-server" the config file in /etc/vmware/ gets overwritten without any warning. Is there some way to get around this? I use cpu scaling on my AMD64 and need the following lines in my /etc/vmware/config to keep the guest OS's clock correct: host.cpukHz = 2000000 host.noTSC = TRUE ptsc.noTSC = TRUE How can this be handled by etc-update? Reproducible: Always Steps to Reproduce: 1. Modify /etc/vmware/config1 2. emerge vmware-server 3. Look at the overwritten /etc/vmware/config Actual Results: Config file is overwritten. Expected Results: It'd like that etc-update picks up this change. (It's an ebuild issue so emerge --info should be irrelevant)
Uhm? It's not even installed by the ebuild, it's generated when you run emerge --config or vmware-config.pl; so no, this can't be handled by CONFIG_PROTECT at all.
Pardon my ignorance, I'm sorry. Thanks Jakub!