On Sun, 5 Jan 2014 10:16:20 +0000 Neil Bothwick <n...@digimed.co.uk> wrote:
> On Sun, 5 Jan 2014 11:36:20 +0200, Gevisz wrote: > > > > > I was afraid to run etc-update as man says it will replace > > > > everything automatically. However, I run dispatch-conf and it > > > > does not see any problems at /etc/ssh, which have only the > > > > following three files: moduli, ssh_config, sshd_config (though > > > > I have added /etc/ssh to CONFIG_PROTECT_MASK). > > > > > > Why did you do that? By masking out config file protection > > > for /etc/ssh there will never be anything to be managed by > > > etc-update as you have told portage to replace those files > > > blindly and without asking. > > > > From man "dispatch-conf": > > CONFIG_PROTECT_MASK is a make.conf setting, read that man page. It > means your config files are overwritten at install time, way be for > you run dispatch-conf or one of its friends. The man page for make.conf actually refers to the CONFIGURATION FILES section of emerge man page. There, indeed, everything explained very clearly and in details. However, it does not work so for my system. Thus, I have the following settings $ echo $CONFIG_PROTECT /usr/share/gnupg/qualified.txt $ echo $CONFIG_PROTECT_MASK /etc/gentoo-release /etc/sandbox.d /etc/fonts/fonts.conf /etc/terminfo /etc/dconf /etc/ca-certificates.conf /etc/texmf/web2c /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/revdep-rebuild but, nevertheless, I see the usual "protected" behavior for all config files in my /etc directory and its subdirectories, that is, instead of overriding them while running emerge world, the system creates the corresponding ._cfg????_* files. And this, in my view, contradicts with the following statement from emerge man pages: "Protected directories are set using the CONFIG_PROTECT variable", as in my case /etc have not been set in my CONFIG_PROTECT variable. > > dispatch-conf will check all directories in the CONFIG_PROTECT > > variable. All config files found in CONFIG_PROTECT_MASK will > > automatically be updated for you by dispatch-conf. > > > 3) I will continue to do this job manually with gvimdiff as I have > > found it much more convenient than dispatch-conf (gvimdiff shows > > the differences a way much better). > > I prefer conf-update but most of these tools allow you to specify your > own diff program if you don't like the default. I use colordiff with > conf-update. Ok, thank you. I will try some of these tools together with gvimdiff when I will have to update my config files in the future.
