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 1EAGd5-0001Kt-Qw for garchives@archives.gentoo.org; Wed, 31 Aug 2005 00:39:04 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7V0ZwnO018791; Wed, 31 Aug 2005 00:35:58 GMT Received: from smtp101.biz.mail.re2.yahoo.com (smtp101.biz.mail.re2.yahoo.com [68.142.229.215]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7V0UCrA014528 for ; Wed, 31 Aug 2005 00:30:13 GMT Received: (qmail 21763 invoked from network); 31 Aug 2005 00:32:23 -0000 Received: from unknown (HELO host2-03.systura.home) (sean@systura.com@209.162.225.44 with plain) by smtp101.biz.mail.re2.yahoo.com with SMTP; 31 Aug 2005 00:32:23 -0000 From: Sean Higgins To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How to work with etc-updates. Date: Tue, 30 Aug 2005 17:19:40 -0400 User-Agent: KMail/1.8.2 References: <43146614.6000002@nethere.com> <1125417989.12459.43.camel@localhost> <20050830182242.04da60f6@hactar.digimed.co.uk> In-Reply-To: <20050830182242.04da60f6@hactar.digimed.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508301719.40231.sean@systura.com> X-Archives-Salt: e4dca51b-fb4e-4b6c-8a9d-447136398621 X-Archives-Hash: df71bbc8843491d656a16e77597f7285 On Tuesday 30 August 2005 01:22 pm, Neil Bothwick wrote: > On Tue, 30 Aug 2005 12:06:29 -0400, Eric Crossman wrote: > > While I agree that etc-update is a vast improvement over other package > > systems, it would be nice to have a CVS type merge where I only have to > > make choices when the "system can't figure it out". It seems like > > etc-update (and friends) should be able to take advantage of mtime > > metadata and md5 checksums to determine if I've made any modifications > > to the default config file. That way an unmodified default config from > > version N can just safely be replaced with the new default for version N > > +1. Does this functionality already exist with the current etc-update? > > It exists as an option with dispatch-conf, as do options to automatically > replace files if the only differences are whitespace and comments. But, it does not automatically do an update if the original file has not changed. That would be a cool feature. How often are files changed, for example in /etc/init.d, but you have not changed that file? I would love the option to automatically update any configuration file that I did not change from the original install. Right on Eric! Sean -- Sean Higgins, sean@systura.com http://www.systura.com - "Where information becomes knowledge." -- gentoo-user@gentoo.org mailing list