14:18 ale 

Remove obsolate port (use mail/vpopmail).

05:10 marcus 

Bump PORTREVISION on all ports that depend on gettext to aid with upgrading.

(Part 1)

16:07 roam 

Remove pkg-comment files in my ports.

13:15 roam 

Fix the regular expressions used for setting the database access
(username, password, database name, etc) - when I did the changeover
from ${PERL} to ${REINPLACE_CMD}, I plain forgot that sed does not
really like Perl-style $1 subexpression references :(

Reported by:    Ventsislav Velkov <veno@evrocom.net>,
                "Pavel Novikov" <pavel@ext.by>

16:55 roam 

USE_REINPLACE.

The mail/vpopmail and mail/vpopmail-stable ports retain their Perl
dependency, since the pkg-install script is written in Perl.  I think
this might need to be changed when I get the time to look into it.

Submitted by:   Ulrich Spoerlein <q@uni.de>

19:55 roam 

Apply a blessed +3 magic wand of autotools protection; a rogue run of
autoconf or automake over our local patches can ruin your whole day.
This rarely, if ever, affected the vpopmail ports, causing mysterious
failures at install time, but inevitably killed the stunnel build if
automake-1.5 happened to be installed.

Reported by:    Dan Langille <dan@langille.org> for stunnel,
                Sitchin Zech <mailsagan@yahoo.com> for vpopmail

09:45 roam 

Create a vpopmail-stable port after a repocopy.  The purpose of this
port is to provide easy access to the 'stable' vpopmail branch
(currently 5.2.x), which, while missing some features, may be considered
safer for deployment on production systems.

The main mail/vpopmail port will shortly be updated to the current
development version - 5.3.6 - which, among other things, reintroduces
APOP support, which was removed earlier in the 5.2 branch, and which the
current stable version - 5.2.1 - does not have.  IMHO, vpopmail-5.3.6 is
stable enough for production use, but since this may not be true for
future development versions, this vpopmail-stable port was created.

Repocopy by:    joe