- Remove lang/python as implicit build and run dependency from

  bsd.python.mk

  Ports need to use a designated python interpreter, whether this
  is the default one chosen by the user (or provided by the system)
  and pulled in via USE_PYTHON[_BUILD|_RUN]=yes or an explicit version
  or version range pulled in via USE_PYTHON[_BUILD|_RUN]=X.Y does not
  matter.

  Ports should however not rely on 'python' at build or installation
  time, whenever possible to avoid problems with building packages for
  different python versions.

  This change tries to raise the barrier for misbehaving ports and eases
  package builds for different python versions.

Tested with:	exp-run (ports/184591)
Reviewed by:	wg@, koobs@
Supported by:	wg@
With hat on:	python@

1 files changed, 22 insertions, 0 deletions

diff --git a/CHANGES b/CHANGES
index 0d75a65b4aaa..e20055f810ec 100644
--- a/CHANGES
+++ b/CHANGES
@@ -10,6 +10,28 @@ in the release notes and/or placed into UPDATING.
 
 All ports committers are allowed to commit to this file.
 
+20131218:
+AUTHOR: mva@FreeBSD.org
+
+  lang/python (and as such the 'python' binary and accomplices)
+  has been removed as default dependency for the USE_PYTHON,
+  USE_PYTHON_BUILD and USE_PYTHON_RUN knobs.
+
+  Ports need to use a designated (default) python interpreter
+  to build and install and in most cases for execution in the user
+  environment. Ports that install python scripts, which are not
+  limited to a certain python version (or version range), can
+  include lang/python as build and/or run dependency.
+
+  USE_PYTHON=yes and similar knobs will only pull in the
+  default python version (e.g. lang/python27), but none
+  of the meta ports or lang/python itself.
+
+  Please use lang/python as build or run-time dependency only,
+  if there is no other way to get a port working properly, since
+  the usage of lang/python complicates package builds for different
+  python versions.
+
 20131213:
 AUTHOR: tijl@FreeBSD.org