07:54 antoine 

Deprecate a few ports

With hat:	portmgr

 

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:00 mat 

Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.

With hat:	portmgr
Sponsored by:	Absolight

 

16:04 mva 

- Convert ports of devel/ to USES=python

Approved by:	portmgr (implicit)

 

19:32 antoine 

- Stage support
- Use PYDISTUTILS_AUTOPLIST

 

19:04 cs 

Give my bzr plugin ports back to pool.

 

17:03 bapt 

Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 1)

 

20:42 cs 

Bump PORTREVISION to reflect name change from devel/bazaar-ng --> devel/bzr

14:59 cs 

Update to 1.4

Approved by:    glarkin@ (mentor)

16:29 cs 

Update to 1.3

Approved by:    glarkin@ (mentor)

12:33 cs 

Change maintainer address to my FreeBSD address

Approved by:    wen@ (mentor)

14:51 glarkin 

The Bazaar pipeline plugin helps you organize your changes into
sections called "pipes". Pipelines can help you:

* focus on each set of changes as a coherent piece, without being
  distracted by other sets of changes.
* respect diff size limits when submitting changes
* avoid reviewer fatigue when submitting changes for code review
* maintain a set of patches against an upstream branch

WWW: http://wiki.bazaar.canonical.com/BzrPipeline

PR:             ports/152305
Submitted by:   Carlo Strub <c-s at c-s.li>