From: Roger Light <rogerlight@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to work with etc-updates.
Date: Tue, 30 Aug 2005 15:31:17 +0100 [thread overview]
Message-ID: <83e036b0050830073171e3b5f7@mail.gmail.com> (raw)
In-Reply-To: <43146614.6000002@nethere.com>
On 30/08/05, Jerry Turba <jturba@nethere.com> wrote:
> As I understand the process etc-update lists new configuration files
> provided by the program authors. I have tried to define some rules for
> myself to determine how to handle these new files.
>
> 1. If I made a change to a file I will never allow the new config file
> to overwrite the old file.
This isn't really a good idea. There are definitely cases where the
new file will provide important updates that you need. Not updating
the config file could lead to the associated program no longer working
or you missing out on a useful feature.
Using etc-update, select the file you have changed and look at the
differences. You may see that other than the changes you made, there
are only updates to comments within the file. In this case you can of
course just ignore the update.
If there are real updates and your own update looks as though it is
still valid then use the "Interactively merge original with update"
option. You can then choose which lines to include in the new file.
The left hand side of the diff output is the original file, the right
hand side is the new. So for each line presented, apart from for the
lines that you have modified, input "r" to choose the right hand side
line. For the lines you changed, input "l" to choose your version.
Always verify the resulting file with "Show differences between merged
file and original" before selecting the "Replace YOUR_FILE with merged
file" option.
All just my opinion of course...
Cheers,
Roger
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-30 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 13:58 [gentoo-user] How to work with etc-updates Jerry Turba
2005-08-30 14:23 ` Mark Knecht
2005-09-01 0:46 ` Jerry Turba
2005-09-01 3:16 ` Mark Knecht
2005-09-01 8:09 ` Neil Bothwick
2005-10-31 17:33 ` Boyd Stephen Smith Jr.
2005-08-30 14:31 ` Roger Light [this message]
2005-08-30 14:46 ` Holly Bostick
2005-08-30 16:06 ` Eric Crossman
2005-08-30 17:15 ` Tony Davison
2005-08-30 17:22 ` Neil Bothwick
2005-08-30 21:19 ` Sean Higgins
2005-08-31 9:10 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83e036b0050830073171e3b5f7@mail.gmail.com \
--to=rogerlight@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox