15:25 antoine 

Deprecate a few ports

With hat:	portmgr

 

19:02 sunpoet 

Cosmetic change

 

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

 

18:45 sunpoet 

Change from py-sqlalchemy11 to py-sqlalchemy12

- Bump PORTREVISION for dependency change

 

20:34 sunpoet 

Change from USES=python:2 to USES=python:2.7

- Bump PORTREVISION for dependency change

 

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

 

15:34 sunpoet 

- Update RUN_DEPENDS: use newer py-sqlalchemy
- Bump PORTREVISION for dependency change

 

03:50 sunpoet 

- Update RUN_DEPENDS
- Add NO_ARCH
- Bump PORTREVISION for dependency change

 

10:52 matthew 

Reorganise and modernise the py-sqlalchemy ports.

 - Introduce new ports for the sqlalchemy 0.9 and 1.0 release branches.
 - Deprecate the ports for the 0.6 and 0.7 release branches, as these
   have been declared EoL and are no longer supported by upstream.
 - Update to the latest available version in each branch.

In detail:

   Port                 Version Maintainer
   ----------------------------------------------
   py-sqlalchemy06      0.6.9   nivit@FreeBSD.org (Deprecate 2016-08-20) [1]
   py-sqlalchemy07      0.7.10  nivit@FreeBSD.org (renamed py-sqlalchemy,
Deprecate 2016-08-20) [1]
   py-sqlalchemy08      0.8.7   nivit@FreeBSD.org (renamed py-sqlalchemy-devel)
[1]
   py-sqlalchemy09      0.9.10  m.tsatsenko@gmail.com (new, repocopy from
py-sqlalchemy-devel) [2]
   py-sqlalchemy10      1.0.13  m.tsatsenko@gmail.com (new, repocopy from
py-sqlalchemy-devel) [2]

 - Use options-helpers and option dependent make targets.
 - Use autoplist for documents as well as python code
 - Add all the docments to the packages: previously an arbitrary
   subset was added in a way that excluded CSS, images and other HTML
   assets.
 - Use TEST_DEPENDS and add a TEST_TARGET instead of having a 'TEST'
   option.
 - Use py-pytest for 0.9.x and later, rather than py-nose.
 - Add CONFLICTS_INSTALL between all of the py-sqlalchemyXY ports.

PR:		191442
Submitted by:	robak
Reviewed by:	robak
Reviewed by:	pi
Approved by:	nivit (maintainer timeout, ~300days) [1]
Approved by:    m.tsatsenko@gmail.com (maintainer) [2]
Sponsored by:	https://reviews.freebsd.org/D908

 

14:00 mat 

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

With hat:	portmgr
Sponsored by:	Absolight

 

03:43 sunpoet 

- Convert PYTHON_FEATURES to USE_PYTHON (which was landed several hours ago)

Notified by:	koobs, wg

 

03:00 sunpoet 

- Use USES=python

 

16:36 sunpoet 

- Add py-geoalchemy 0.7.2

GeoAlchemy is an extension of SQLAlchemy. It provides support for Geospatial
data types at the ORM layer using SQLAlchemy. It aims to support spatial
operations and relations specified by the Open Geospatial Consortium (OGC).

WWW: https://pypi.python.org/pypi/GeoAlchemy