From owner-freebsd-questions@FreeBSD.ORG Wed Sep 3 14:37:33 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9465C16A4BF; Wed, 3 Sep 2003 14:37:33 -0700 (PDT) Received: from lakemtao01.cox.net (lakemtao01.cox.net [68.1.17.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A20743F85; Wed, 3 Sep 2003 14:37:32 -0700 (PDT) (envelope-from A.J.Caines@halplant.com) Received: from mail.halplant.com ([68.98.167.210]) by lakemtao01.cox.net (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with ESMTP id <20030903213731.QAOY722.lakemtao01.cox.net@mail.halplant.com>; Wed, 3 Sep 2003 17:37:31 -0400 Received: by mail.halplant.com (Postfix, from userid 1001) id: 37:31 -0400 (EDT) Date: Wed, 3 Sep 2003 17:37:31 -0400 From: Andrew J Caines To: BSD Questions Message-ID: <20030903213731.GB19379@hal9000.halplant.com> Mail-Followup-To: BSD Questions , ports@FreeBSD.org References: <3F55B8D1.7010502@ant.uni-bremen.de> <20030903171754.GA13343@graf.pompo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030903171754.GA13343@graf.pompo.net> Organization: H.A.L. Plant X-PGP-Fingerprint: C59A 2F74 1139 9432 B457 0B61 DDF2 AA61 67C3 18A1 X-Powered-by: FreeBSD 4.8-STABLE X-URL: http://halplant.com:88/ X-Yahoo-Profile: AJ_Z0 Importance: Normal User-Agent: Mutt/1.5.4i cc: ports@FreeBSD.org Subject: Re: Configuration files after portupgrade horde and imp X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew J Caines List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2003 21:37:33 -0000 Thierry, > This is a known problem, and unfortunately, I have not yet found a > satisfying solution. Usually, the configuration files of a release n > don't work anymore with release n+1. It's not clear from Heinrich's message, but if this was a major version upgrade, then a pkg-message saying that the original config files have been backed up would be appropriate. If you're overwriting the original config files on each install (as I suspect), then that is wrong. It would be appropriate to save distributed config files to another location - eg. .default, .dist or similar, perhaps with an informative pkg-message. > Actually, we would need a kind of mergemaster... Quite a few apps either know how to update their own configs or provide tools to assist. This is not really a ports issue. > Any better ideas or patches are welcome! I would try to offer a patch, but I don't know nearly enough about this port to help. It should be simple enough not to overwrite config files (and any other files an install should never touch) and to write a suitable pkg-message. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@halplant.com | | "They that can give up essential liberty to obtain a little temporary | | safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 |