16:31 antoine 

Deprecate more parts of zope 2.13 stack

With hat:	portmgr

 

17:05 mat 

Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight

 

15:50 mat 

Convert Python ports to FLAVORS.

  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

 

14:16 mat 

Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p.

With hat:	portmgr
Sponsored by:	Absolight

 

21:07 rm 

Update Zope to 2.13.23.

This update also includes:
- devel/py-Acquisition 4.0a1 -> 4.2.1
- devel/py-ExtensionClass 4.0a1 -> 4.2.1
- devel/py-Products.BTreeFolder2 2.13.4 -> 2.14.0
- devel/py-Products.ExternalMethod 2.13.0 -> 2.13.1
- mail/py-Products.MailHost 2.13.1 -> 2.13.2
- devel/py-Products.StandardCacheManagers 2.13.0 -> 2.13.1
- devel/py-zconfig 2.9.3 -> 3.0.4
- devel/py-zLOG 2.11.1 -> 2.11.2

Changes common across this ports: add LICENSE_FILE, add NO_ARCH, sort USE_PYTHON

MFH:		2015Q3

 

17:10 mva 

- Convert ports of mail/ to new USES=python

Approved by:	portmgr (implicit)

 

06:24 antoine 

Unbreak

 

16:25 bapt 

Convert m* to USES=zip

 

23:40 rm 

- do not use easy_install, convert to auto-generated packing list
- move DIST_SUBDIR upper, where appropriate
- add trailing slash to WWW url, where appropriate
- bump PORTREVISION

 

19:59 bapt 

Add NO_STAGE all over the place in preparation for the staging support (cat:
mail)

 

10:33 rm 

- transfer maintainership for my zope-ports to zope@
- add them to virtual category `zope'

22:20 rm 

Change email for my ports to FreeBSD one.

Approved by:    novel (mentor)
Feature safe:   yes

07:57 wen 

The MailHost product provides support for sending email from within
the Zope environment using MailHost objects.

WWW: http://pypi.python.org/pypi/Products.MailHost/

Submitted by:   Ruslan Mahmatkhanov <cvs-src@yandex.ru> (via github)