From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.43)
id 1EA7Du-0002r8-Hd
for garchives@archives.gentoo.org; Tue, 30 Aug 2005 14:36:26 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7UEWDi7018305;
Tue, 30 Aug 2005 14:32:13 GMT
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205])
by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7UELisN024366
for <gentoo-user@lists.gentoo.org>; Tue, 30 Aug 2005 14:21:44 GMT
Received: by zproxy.gmail.com with SMTP id x7so786881nzc
for <gentoo-user@lists.gentoo.org>; Tue, 30 Aug 2005 07:23:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=JH8Y9/K15MNTCJeSe0n7KenYx0zfuV3j3Xyf0ijWB1lNU1JxrgkcotyOPNM0yUpPKjIFTG4sFH/3lZnDnhwVoosZ9EvPcwML0pf7gHTPXdd2tYYNcpHgGQwFWUztDPPPz7zhPIPn5JwxVqnodu4qO36T7xNViwxZiNahqIVHjQc=
Received: by 10.36.58.14 with SMTP id g14mr500005nza;
Tue, 30 Aug 2005 07:23:50 -0700 (PDT)
Received: by 10.36.60.4 with HTTP; Tue, 30 Aug 2005 07:23:50 -0700 (PDT)
Message-ID: <5bdc1c8b050830072344fa76c1@mail.gmail.com>
Date: Tue, 30 Aug 2005 07:23:50 -0700
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to work with etc-updates.
In-Reply-To: <43146614.6000002@nethere.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <43146614.6000002@nethere.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j7UELisN024366
X-Archives-Salt: d7fd9774-a70d-4144-b6a6-0e6688919272
X-Archives-Hash: cebbb49687d51848e6b88cf84a6a85ec
On 8/30/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.
I know one person who operated like this but I didn't agree. I think
that you have to (eventually) do the update. The developers change
things in these files also. If you don't change you don't get the
updates, or things (possibly) don't get activated.
>
> 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?
>
My rules are:
1) The update was put there for a reason.
2) If it's a file in /etc/initd then I update it automatically.
3) If it's a file in /etc/conf.d then I update it very carefully.
4) If it's a file in /etc/, /etc/X11, or elsewhere the I update it
very carefully but possibly not right now.
5) Anything else, I go slow. Maybe I look for messages from others on
this list having problems before I do something.
My experience is that rules 2 & 3 account for 80-90% of the updates.
Cheers,
Mark
--
gentoo-user@gentoo.org mailing list