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

 

17:49 sunpoet 

Update to 1.5

Changes:	https://github.com/jaraco/backports.functools_lru_cache/blob/master/CHANGES.rst

 

16:00 sunpoet 

Clean up Makefile

 

15:00 lifanov 

add devel/py-backports - namespace shim for Python backports

Currently, all py-backports.* ports conflict with each other
over a file that has the same contents.

This creates a port that installs the shared file and py-backports.*
ports should depend on this one and remove the shared file from their
own pkg-plist. It's the same approach as the one taken by OpenBSD.

Some ports are already converted as an example:
- security/py-backports.ssl_match_hostname
- devel/py-backports.functools_lru_cache
- devel/py-backports.shutil_get_terminal_size

The last two conversions and the fix to work with FLAVORS were submitted
by antoine. Thank you!

Reviewed by:	antoine
Approved by:	portmgr (antoine)
Differential Revision:	https://reviews.freebsd.org/D11095

 

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

 

13:16 sunpoet 

Update to 1.4

Changes:	https://github.com/jaraco/backports.functools_lru_cache/blob/master/CHANGES.rst

 

11:07 sunpoet 

Take maintainership

- Add NO_ARCH
- Update COMMENT
- Update pkg-descr
- Add PyPI as primary WWW

 

22:27 rene 

Reset mva@'s ports, he handed in his ports bit.

 

17:50 mva 

A backport of the lru_cache function from Python 3.3's functools.

WWW: https://github.com/jaraco/backports.functools_lru_cache