Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

When updating a package using emerge or ebuild, how do I avoid clobbering my config files?

April 26, 2017avoid clobbering config emerge files package updating

0

0 Posted

When updating a package using emerge or ebuild, how do I avoid clobbering my config files?

1 Answer

0

0 Posted

Portage now includes config file management support by default. Type emerge –help config for more details. The (overly) simple answer is that if a package installs foo somewhere under /etc, and another foo already exists there, then the new foo will instead be renamed to ._cfgxxxx_foo in that directory. A useful tool for examining and updating any protected config files is etc-update, currently obtained by emerge app-admin/gentoolkit.