Number of commits found: 13

Add more PLIST_SUB to Mk/Uses/python.mk

- Add PYTHON_PYOEXTENSION and PYTHON_SUFFIX
- Add PYTHON2 and PYTHON3
- Respect PYTHON_VERSION
- Rename PYOEXTENSION to PYTHON_PYOEXTENSION

This change would help:
- Build databases/postgresql*-plpython with Python 3
  (It has PLIST issue since bsd.python.mk to Uses/python.mk transition)
- Simplify Makefile

PR:		205807
Differential Revision:	https://reviews.FreeBSD.org/D4758
Exp-run by:	antoine

Let gnome3 stack be built with python 3.5

This mostly fixing packaging for python3.5, but there is
also py35 waf fix for py3-cairo, that was obtained from Ubuntu
repository.

PR:		204075
Approved by:	maintainer timeout (22 days)

Improve shebangfix framework

- Support multiple values in *_OLD_CMD, i.e. we can now fix both
"/usr/bin/python" and "/usr/bin/env python" at the same time
- Default *_OLD_CMD values are now always appended, so you don't need to specify
them in individual ports
- Add lua support (depends on USES=lua)
- Add more default values, such as "/usr/bin/env foo" for python, perl, bash,
ruby and lua
- Shebangfix now matches whole words, e.g. we will no longer (erroneously)
replace "/usr/bin/perl5.005" with "${perl_CMD}5.005" (but "/usr/bin/perl -tt" is
still (correctly) replaced with "${perl_CMD} -tt")

Note that *_OLD_CMD items containing spaces must now be quoted (e.g.
perl_OLD_CMD=/bin/perl /usr/bin/perl "/usr/bin/env perl")

Update shebangfix usage according to new rules in many ports:

- Remove *_OLD_CMD for patterns now replaced by default
- Quote custom *_OLD_CMD which contain spaces

Fix shebangfix usage in many ports (irrelevant to infrastructure change):

- Remove redundant SHEBANG_LANG (no need to duplicate default langs)
- Remove redundant *_CMD (such as
python_CMD=${LOCALBASE}/bin/python${PYTHON_VER} when USES=python is present)
- Never use *_OLD_CMD in REINPLACE_CMD matchers, these should always look for
exact string

Approved by:	portmgr (bapt)
Differential Revision:	D3756

Add a new USES=waf to handle the waf building system, allowing to factorise code
Plug waf into MAKE_CMD and CONFIGURE_CMD so the regular defined targets can be
reused

Always define _MAKE_JOBS so that when bsd.port.mk will stop overwritting
_MAKE_JOBS when parallel jobs are disabled we can enforce -j1 (which is needed
to really disable parallelisation with waf

WAF_CMD has been created to allow one to override the location of the waf script
relatively to WRKSRC

CONFIGURE_TARGET is by default defined to "configure"
ALL_TARGET is by default defined to "build"
INSTALL_TARGET is by default defined to "install"

USES=waf is by default stagedir safe

Switch default python3 version from 3.3 to 3.4.
Bump PORTREVISIONs for the affected ports.

Exp-run by:	antoine

Make py3-cairo build with python 3.4.

Submitted by:	antoine@

- Convert ports of graphics/ to new USES=python

Approved by:	portmgr (implicit)

Don't hardcode python version.

Submitted by:	makc@

Rework python module compile so it doesn't code the stagedir in it [1]

While here switch to USES=tar:bzip2
Remove waf from SHEBANG_FILES. it contains binary so running sed on it
 not guaranteed to work as intended. [2]
Prefix waf commands with PYTHON_CMD so it run with the correct python version.
Use the waf --destdir command for destdir
Remove configure_ENV because they are already set.
Use post-patch to dynamicly fix the python version in test/examples_test.py
 instead of a patch.

Reported by:	swills@ [1], mva [2]

Do what was clearly intended: s/${ENV}/${SETENV}/

Prior to this change these ports fail when built under su(8) since that
results in ${ENV} being ~/.shrc.

Approved by:	kwm (maintainer, gnome@)

Add forgotten NO_STAGE keyword.

Disable stage for now until I can figure out how to make it work with waf.

Submitted by:	Kenta Suzumoto <kentas@hush.com>

Add python cairo 1.10.0 for python 3.

Number of commits found: 13

13 vulnerabilities affecting 73 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities