Re: [gentoo-user] Re: default CONFIG_PROTECT behavior

[Peter Humphrey]

On Sunday, 17 June 2018 18:12:11 BST Mick wrote:
> On Sunday, 17 June 2018 18:08:48 BST Ian Zimmerman wrote:
> > On 2018-06-17 12:42, Andrew Udvare wrote:
> > > On 06/17/2018 12:17 PM, Ian Zimmerman wrote:
> > > > What happens to files within the scope of CONFIG_PROTECT if I don't
> > > > execute dispatch-conf or any similar thingy?  I have found the
> > > > confusion the latter tool generates completely unsurmountable.
> > >
> > > I think the side-by-side merger is very easy for small changes. Most
> > > of the time I press z because I don't need the new changes.
> >
> > It's not the merge step itself (sdiff) that is confusing, it's what
> > dispatch-conf does afterward with the result.  When you used it the
> > first time, did you understand what "zap new" means?
>
> From the fine manual:
>
>  z      Zap (delete) the new config file and continue.
>
>
> For files which have a lot of changes, some of which I wish to reject and
> some to accept, I tend to use m (for merging).  Again from the fine manual:
>
> m      Interactively merge the current and new config files.
>
> > And yes, I was driven to ask this after I got an update that wasn't
> > "small".
> >
> > > find /etc/ -iname '._cfg*'
> > >
> > > Or what dispatch-conf does:
> > >
> > > find /etc -iname '._cfg????_*' ! -name '.*~' ! -iname '.*.bak' -print
> >
> > Thanks for this information.

I don't have any of those problems. I still use etc-update, and if there are 
complex updates I edit the original file myself, using the diff as a guide.

I never did get to grips with the more "modern" ways of doing it.

-- 
Regards,
Peter.