From owner-freebsd-ports@FreeBSD.ORG Sun Apr 9 20:10:16 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6757716A400 for ; Sun, 9 Apr 2006 20:10:16 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from graf.pompo.net (graf.pompo.net [81.56.186.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 966F643D45 for ; Sun, 9 Apr 2006 20:10:15 +0000 (GMT) (envelope-from thierry@pompo.net) Received: by graf.pompo.net (Postfix, from userid 1001) id 5D13111431; Sun, 9 Apr 2006 22:10:12 +0200 (CEST) Date: Sun, 9 Apr 2006 22:10:12 +0200 From: Thierry Thomas To: "Marc G. Fournier" Message-ID: <20060409201012.GF93845@graf.pompo.net> Mail-Followup-To: "Marc G. Fournier" , freebsd-ports@freebsd.org References: <20060407032220.W947@ganymede.hub.org> <1144391457.23833.6.camel@shumai.marcuscom.com> <44363371.9050200@fromley.net> <20060407141831.GA65673@pentarou.parodius.com> <20060408075305.GB58919@graf.pompo.net> <20060409050018.X1096@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060409050018.X1096@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-PRERELEASE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 Cc: freebsd-ports@freebsd.org Subject: Re: BEWARE upgrading Horde System X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 20:10:16 -0000 Le Dim 9 avr 06 à 10:03:35 +0200, Marc G. Fournier écrivait : > Actually, I think you've done a fine job ... my *only* beef is arbitrarily > moving aside of the config files that I've already configured ... if I > download a horde package, and untar that over top of my existing setup, to > upgrade, *it* doesn't do it ... and if I use CVS to update from the > anoncvs server, it doesn't remove my config files ... the FreeBSD port > shouldn't either ... There are two main possibilities: 1- the current one: you get an almost running webmail after the initial installation; the installed config files are pre-configured with the variables set in the ports Makefile and according to the installed dependencies. When upgrading, your modified config files are saved, and a new config is installed. Then you have to merge your setup within the new files (there is no mergemaster: I use gvimdiff, and I'm sure that any decent $EDITOR provides such a tool). You have to do that only for your modified files (those saved as .previous). 2- the port does not pre-install config files, but only the .dist files as samples. As you write, this is the method provided by the Horde project when you install manually directly from the tarball. During the initial configuration, the OP must cd config/ for f in *.dist; do cp $f `basename $f .dist`; done for each Horde module. Since these files are not installed by the port, they are not deinstalled, and they are still ready when you reinstall. And your installation may run or not... To be secure, you have to compare your configured files with the new .dist files, and merge the new options into your files. You have to check all config files, even the ones that you kept unmodified. I had choosen the first method, because I thought it was easier for the OP this way, and I think that a port should do better than a manual installation. Regards, -- Th. Thomas.