Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Jul 2003 12:29:05 -0700 (PDT)
From:      Doug Barton <DougB@FreeBSD.org>
To:        Mark Edwards <mark@antsclimbtree.com>
Cc:        ports@FreeBSD.org
Subject:   Re: FreeBSD Port: p5-Mail-SpamAssassin-2.55
Message-ID:  <20030701122508.E12287@12-234-22-23.pyvrag.nggov.pbz>
In-Reply-To: <BA68C26F-ABF0-11D7-B3DC-000393C0ABC0@antsclimbtree.com>
References:  <BA68C26F-ABF0-11D7-B3DC-000393C0ABC0@antsclimbtree.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030701122508.E12287>