Bug 9040

Summary:	Files in /etc don't get overwritten even with CONFIG_PROTECT set
Product:	Portage Development	Reporter:	Christian Birchinger (RETIRED) <joker>
Component:	Unclassified	Assignee:	Daniel Robbins (RETIRED) <drobbins>
Status:	RESOLVED INVALID
Severity:	normal	CC:	carpaski, h3y
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Christian Birchinger (RETIRED) gentoo-dev

2002-10-12 09:37:42 UTC

(bash-completion portage is installed on the system)

~$ echo "# lame addon" >>/etc/bash_completion
~$ grep "# lame addon" /etc/bash_completion
# lame addon
~$ export CONFIG_PROTECT=""
~$ emerge bash-completion

<... lots of emerge output ...>

~$ grep "# lame addon" /etc/bash_completion
# lame addon
~$

So even with CONFIG_PROTECT="" it does *not* overwrite the file in /etc
The only thing i've seen is an "o" flag on the install part:
<...>
--- /etc/
-o- /etc/bash_completion
--- /etc/bash_completion.d/
<...>

It does not matter if the env variable or a line in make.conf is used to
define CONFIG_PROTECT="". In either way the file bash_completion in /etc
does not get overwritten. With a disabled protection it should overwrite
everything i think.
The option CONFIG_PROTECT="" seems not complettly ignored, because the
"._cfg"-files are not being created (that's the correct thing).

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2002-10-13 08:43:03 UTC

CONFIG_PROTECT="-*" ---  does what you want.

CONFIG_PROTECT is an incremental variable, and isn't cleared by
CONFIG_PROTECT="" --- That only affects entries attained from
/etc/env.d

Working on fixing the docs to be more explicit about this one.