From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MBkvu-0005QE-7U for garchives@archives.gentoo.org; Wed, 03 Jun 2009 07:30:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4CD66E041B; Wed, 3 Jun 2009 07:30:44 +0000 (UTC) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by pigeon.gentoo.org (Postfix) with ESMTP id 08E22E041B for ; Wed, 3 Jun 2009 07:30:43 +0000 (UTC) Received: by ewy9 with SMTP id 9so8615496ewy.34 for ; Wed, 03 Jun 2009 00:30:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=g8i+cuSrcH4iSlHE45f9BXAr0ypYNNkTFzMjnMYURv0=; b=wfR3elN15F7Squ5YmisoFScI1MkFMp1JUU8Z5yKMRQejAzfhtakd1lm9b2vVHykdK/ pntqlNN6z0C2Hb/koKGp2ektwhs904Cg9gjTQmKL16cArmJqMw50V+mCqR4SPwGIji7k 2Vp1pDZ1BCcpH+1VEW2mjNVvE3le/ZEvQyt3c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=ocXoAS5D6NCPyq+h7kteyd0YyrU+mr8QThs3pkEmqPsk0HG1tCrl/Ns4s1BphZyYTD 63tfszom0CbQhgmP2Jjf9hxvhQCw0A73GacPoB/awWEa8m2FEoROkY7ddsNBLkzB6ka0 8Eb4lT2my67wuiaX3pTIhZf8Kq0TuXoAOc/98= Received: by 10.210.136.15 with SMTP id j15mr1746600ebd.86.1244014243355; Wed, 03 Jun 2009 00:30:43 -0700 (PDT) Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94]) by mx.google.com with ESMTPS id 12sm637169ewy.55.2009.06.03.00.30.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 03 Jun 2009 00:30:42 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] dispatch-conf merge Date: Wed, 3 Jun 2009 09:30:41 +0200 User-Agent: KMail/1.11.90 (Linux/2.6.29.4r4; KDE/4.2.87; x86_64; ; ) References: <87zlcpc2pl.fsf@newton.gmurray.org.uk> In-Reply-To: <87zlcpc2pl.fsf@newton.gmurray.org.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.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 Message-Id: <200906030930.41380.volkerarmin@googlemail.com> X-Archives-Salt: 08479268-cfff-43f4-a64d-4062c4b99b99 X-Archives-Hash: 32c843d5c30bffbcf665a95952826835 On Mittwoch 03 Juni 2009, Graham Murray wrote: > Is there any way to improve the granularity in the merge function of > dispatch-conf, or make it more intelligent? > > The particular situation where it gives me problems is in configuration > files where the value of an option has been manually changed following > initial installation, then on an upgrade a new option is added close to > the one previously changed. In this situation, dispatch-conf almost > invariably wants to reset the changed option line back to its default. > When selecting 'm' to merge changes it will present a left hand side > with the already existing value (often plus other lines) with the right > hand side with the default lines for both the existing line(s) and the > new ones. try cfg-update. It is way smarter than dispatch-conf.