Re: [gentoo-user] Fw: updating /etc/package.accept_keywords

[Dale]

Neil Bothwick wrote:
> On Thu, 30 May 2019 06:28:41 -0500, Dale wrote:
>
>> This is good advice.  I sometimes look to see if there is anything
>> important to the changes.  Most of the time, it is mostly the date or
>> something at the top, sometimes it even detects that and just does it
>> itself.  Thing is, sometimes I just don't have time to wade through a
>> somewhat large file with a lot of changes that may not be important or
>> even worse, will change settings I made back to defaults that don't
>> work.  Some files I let sit until I can figure out if I need them
>> updated or not.  I'm fond of the zap new button. 
> A tool that shows just the differences, like cfg-update or conf-update,
> makes this easier.
>

Installed both.  Couldn't figure out conf-update, sort of like
dispatch-conf.  I liked cfg-update but got lost.  It opened a window
that had these nifty arrows that moved things from one to the other.  I
prefer moving entries I want to keep to the new file and was able to
figure out how to do that.  Where I got lost, what do I do to save it
and tell it to use the new file?  I didn't see anything in the graphical
part and couldn't figure out how to view the new file before accepting
it when I got back to conf-update.  Other than that, I like the tool and
would like to use it. 


>> A prime example, KDE config files.  I have my desktop set up like I like
>> it.  If I update the config file, it usually sets it back to the
>> default.  That's one I like to spend time on if I update it.  Another is
>> my network configs.  Some settings are done differently and won't work
>> if I use the updated file or it resets to default. 
> KDE config files shouldn't be in CONFIG_PROTECTed directories, it's
> generally configured at user level.

It hasn't done it in a while but it used to clobber that thing on a
regular basis.  Either way, that and a couple other file taught me to be
careful with those updates. 

Dale

:-)  :-)