Date: Sun, 5 Dec 2010 07:51:49 +0000 (UTC) From: Doug Barton <dougb@FreeBSD.org> To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/mail/alpine Makefile pkg-install pkg-plist Message-ID: <201012050751.oB57pneA021148@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
dougb 2010-12-05 07:51:49 UTC
FreeBSD ports repository
Modified files:
mail/alpine Makefile pkg-plist
Added files:
mail/alpine pkg-install
Log:
Remove CONFLICTS for the old pine stuff, it's been long enough
Fix the problem mentioned in the PR related to a feature of the port
that is useful, or dangerous depending on how you look at it. :)
If you run 'alpine -conf > file' it will merge in values from your
existing global conf file (/usr/local/etc/alpine.conf) and spit out a
new file with any new features added. The port used this feature when
I took it over, and I maintained that behavior because it is useful.
However, it is different from the traditional behavior of installing
a clean foo.conf.sample file, and maintaining foo.conf only if it
differs from the sample.
My solution to this problem is different than the PR's, but does not
involve patching the source. Using the pkg-install file and taking
advantage of the default behavior of the alpine -conf feature I have
created the best of both worlds, a clean .sample, and merging in local
changes if they exist.
Since I'm changing stuff anyway, do both sides of the process in a
more security-conscious way.
Bump PORTREVISION since the package is now different
PR: ports/148859
Submitted by: Ganael Laplanche <ganael.laplanche@martymac.com>
Revision Changes Path
1.11 +2 -5 ports/mail/alpine/Makefile
1.1 +32 -0 ports/mail/alpine/pkg-install (new)
1.2 +2 -5 ports/mail/alpine/pkg-plist
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201012050751.oB57pneA021148>