From owner-freebsd-ports@FreeBSD.ORG Tue Jul 1 12:29:06 2003 Return-Path: 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 DBB1C37B401 for ; Tue, 1 Jul 2003 12:29:06 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 717CC43FE3 for ; Tue, 1 Jul 2003 12:29:06 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from 12-234-22-23.client.attbi.com ([12.234.22.23]) by attbi.com (rwcrmhc11) with SMTP id <20030701192906013007u9rpe>; Tue, 1 Jul 2003 19:29:06 +0000 Date: Tue, 1 Jul 2003 12:29:05 -0700 (PDT) From: Doug Barton To: Mark Edwards In-Reply-To: Message-ID: <20030701122508.E12287@12-234-22-23.pyvrag.nggov.pbz> References: Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: p5-Mail-SpamAssassin-2.55 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2003 19:29:07 -0000 On Tue, 1 Jul 2003, Mark Edwards wrote: > On Tuesday, July 1, 2003, at 03:00 AM, Doug Barton wrote: > > > On Mon, 30 Jun 2003, Mark Edwards wrote: > > > >> I just used portupgrade to update my SpamAssassin install, and it > >> hosed > >> my /usr/local/etc/mail/spamassassin/local.cf file. This happened last > >> time I updated too. That is the file that I should use for > >> customizing > >> right? This shouldn't happen right? > > > > I can't speak for portupgrade. If you have version 1.45 of the SA port > > Makefile, this shouldn't happen, no. If you have an earlier version, > > you > > need to update your ports collection. > > Well, I updated to the latest port via cvs (2.55) and I was updating > from 2.5-something, and it definitely wiped my local.cf file. When this issue was first brought to my attention, I made the following changes in the port: grep -i local * Makefile: @${MV} ${WRKSRC}/rules/local.cf ${WRKSRC}/rules/local.cf.sample Makefile: @${SED} -e 's#local.cf#local.cf.sample#g' \ pkg-plist:etc/mail/spamassassin/local.cf.sample I also tested the thing extensively with a dummy local.cf file locally, and it didn't touch it. > The Makefile is version 1.45. I doubt portupgrade is the issue, since > it just triggers the make and make install processes, but maybe I'm > wrong there. In any case, portupgrade is commonly-used, and someone > should fix this problem. Well you're undoubtedly correct about that, but since I'm fairly sure it's not the port, I'm not sure what I'd be fixing. If you can identify what's happening and why, I'll be glad to take another look. Doug -- This .signature sanitized for your protection