Hallo! The config_protect and config_protect_mask can be very helpfull. But there are different descriptions using 'emerge --help config' and in the web. a.) config_protect_mask is related to directorys b.) config_protect_mask is also related to files I can't test it at the moment but I'm suggesting a new 'config_protect_file' variable. Because there are mostly only a few configuration files wich I want to protect and much more I don't. In my special case 10 - 20 files wich I have modified. But about 50 are already in /etc/. Thanks in advance, Thomas
emerge --help config really needs to be updated (and probably moved to a man page). The feature that you want is already supported in >=portage-2.1.2_pre1 (bug 14321). You can add normal files to CONFIG_PROTECT and/or CONFIG_PROTECT_MASK.
Thank you very much for the very fast response! Do I understand right: 1.) The feature "config_protect_file" will be available with >=portage-2.1.2_pre1 (means CONFIG_PROTECT_FILES & CONFIG_PROTECT_FILES_MASK at bug 14321). 2.) Adding normal files to CONFIG_PROTECT and/or CONFIG_PROTECT_MASK is allways available. ("will be" because I have a amd64 and there are only 'sys-apps/portage-2.1.2_preN-releases with ~amd64 keyword at the moment)
CONFIG_PROTECT and CONFIG_PROTECT_MASK are the only two variables for config protection. You can rely on both of those supporting files (in addition to directories) in all versions of portage >=-2.1.2_pre1 (_pre2, _pre3, etc...).
We need to do something about the --help config thing, but that's bug 136908. *** This bug has been marked as a duplicate of 14321 ***
