public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jerry Turba <jturba@nethere.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] How to work with etc-updates.
Date: Tue, 30 Aug 2005 06:58:44 -0700	[thread overview]
Message-ID: <43146614.6000002@nethere.com> (raw)

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.

2. If the new config file is a new default file I will accept the new file.

3. I will never change a file that is program code, (I am not a programmer).

Are these rules sane? What kind of problems could I run into doing this? 
What would be some better rules to use? I have tried dispatch-conf but I 
still have to make the same decisions. Am I missing something?

Thanks for any advice.

Jerry
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2005-08-30 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 13:58 Jerry Turba [this message]
2005-08-30 14:23 ` [gentoo-user] How to work with etc-updates 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
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=43146614.6000002@nethere.com \
    --to=jturba@nethere.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