non port: mail/alpine/pkg-install |
Number of commits found: 3 |
Sunday, 15 Jun 2014
|
08:40 pi
mail/alpine: 2.00 -> 2.11, stagify'ed, portlint'ed, new master site
Big thanks to Michelle for the biggest part of the work in getting
the port to StageAge. Thanks for Marco to take over as maintainer.
PR: ports/190273
Submitted by: Michelle Sullivan <michelle@sorbs.net>
Approved by: Marco Beishuizen <mbeis@xs4all.nl> (incoming maintainer)
|
Wednesday, 8 Dec 2010
|
06:46 dougb
There is no need to include PKGINSTALL in the pico package
Give the alpine/pkg-install script triple protection against
being run inappropriately.
|
Sunday, 5 Dec 2010
|
07:51 dougb
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>
|
Number of commits found: 3 |