fdm is a simple, lightweight replacement for mail fetch, filter and delivery programs such as fetchmail and procmail. It can currently fetch using POP3, POP3S, IMAP or from stdin, and deliver to a pipe, file, maildir, mbox or SMTP server, based on regexps. Author: Nicholas Marriott WWW: http://fdm.sourceforge.net/ xt/html' href='http://www.tfcis.org/~lantw44/cgit/cgit.cgi/freebsd-ports-gnome/commit/?id=b2012f72500300ecbba6933c68717ba52c454563'/> b2012f72500300ecbba6933c68717ba52c454563 FLAVOR is the current port's flavor, it should not be used outside of this scope. Sponsored by: Absolight
FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight
Convert Python ports to FLAVORS. 2017-11-30T15:50:30+00:00 mat mat@FreeBSD.org 2017-11-30T15:50:30+00:00 32512cab3e8dd90b7cd0525bb5dc98007db431e2 Ports using USE_PYTHON=distutils are now flavored. They will automatically get flavors (py27, py34, py35, py36) depending on what versions they support. There is also a USE_PYTHON=flavors for ports that do not use distutils but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if using distutils but flavors are not wanted. A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added to cope with Python ports that did not have the Python PKGNAMEPREFIX but are flavored. USES=python now also exports a PY_FLAVOR variable that contains the current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464
  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the
  current python flavor.  It can be used in dependency lines when the
  port itself is not python flavored.  For example, deskutils/calibre.

  By default, all the flavors are generated.  To only generate flavors
  for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
  BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.

  In all the ports with Python dependencies, the *_DEPENDS entries MUST
  end with the flavor so that the framework knows which to build/use.
  This is done by appending '@${PY_FLAVOR}' after the origin (or
  @${FLAVOR} if in a Python module with Python flavors, as the content
  will be the same).  For example:

    RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}

PR:		223071
Reviewed by:	portmgr, python
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D12464
Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z. 2016-04-01T14:33:55+00:00 mat mat@FreeBSD.org 2016-04-01T14:33:55+00:00 6126a9c5a826afdbe6ebfd5bf6d02c6e2be2a700 With hat: portmgr Sponsored by: Absolight
With hat:	portmgr
Sponsored by:	Absolight
Update plone stack to 4.3.7 2016-01-10T23:10:45+00:00 rm rm@FreeBSD.org 2016-01-10T23:10:45+00:00 6ecc44015c3f9dfab222bf746946cbafcb399694 Changelogs: https://plone.org/products/plone/releases/4.3.3 https://plone.org/products/plone/releases/4.3.4 https://plone.org/products/plone/releases/4.3.5 https://plone.org/products/plone/releases/4.3.6 https://plone.org/products/plone/releases/4.3.7 MFH: 2016Q1 Security: 6b3374d4-6b0b-11e5-9909-002590263bf5
Changelogs:
https://plone.org/products/plone/releases/4.3.3
https://plone.org/products/plone/releases/4.3.4
https://plone.org/products/plone/releases/4.3.5
https://plone.org/products/plone/releases/4.3.6
https://plone.org/products/plone/releases/4.3.7

MFH:		2016Q1
Security:	6b3374d4-6b0b-11e5-9909-002590263bf5