/www/mediawiki17/files/

lished>2021-05-26T12:56:57+00:00 fe5bc91794788b116abe866ac5e032f40e39e1d5

Mk: switch from PYTHON_PORTVERSION to PYTHON_DISTVERSION 2021-05-25T13:55:44+00:00 Dmitry Marakasov amdmi3@FreeBSD.org 2021-04-09T13:28:59+00:00 5f69415313f894338dca54e21b5c3981e5e5f58f This brings python framework in consistense with handbook recommendations to prefer DISTVERSION and simplifies adding prerelease versions of python PR: 255013 Differential Revision: https://reviews.freebsd.org/D29418 Exp-run by: antoine Approved by: wen@, no objection from python@ or portmgr@
This brings python framework in consistense with handbook recommendations
to prefer DISTVERSION and simplifies adding prerelease versions of
python

PR:		255013
Differential Revision:	https://reviews.freebsd.org/D29418
Exp-run by:	antoine
Approved by:	wen@, no objection from python@ or portmgr@
Remove # $FreeBSD$ from Makefiles. 2021-04-06T14:31:07+00:00 Mathieu Arnold mat@FreeBSD.org 2021-04-06T11:55:50+00:00 305f148f482daf30dcf728039d03d019f88344eb

Remove logic for Python < 3.6 for ports using Python 3.6+ 2021-01-11T19:36:17+00:00 Rene Ladan rene@FreeBSD.org 2021-01-11T19:36:17+00:00 75d659b385e30935a659f6c63b86195f2b975175

Drop python 2.7 support from a few ports 2020-12-28T23:02:12+00:00 Antoine Brodin antoine@FreeBSD.org 2020-12-28T23:02:12+00:00 aa7a6c429ea62d972467d6755fa7a6f52256b452 With hat: portmgr
With hat:	portmgr
databases/py-gdbm@py39: fix build on GCC architectures 2020-11-16T15:59:41+00:00 Piotr Kubaj pkubaj@FreeBSD.org 2020-11-16T15:59:41+00:00 c5a9268459fb2943bb3ca4adfc03ee2e7323e616 cc1: error: unrecognized command line option "-Wno-unused-result"
cc1: error: unrecognized command line option "-Wno-unused-result"
Update `databases/gdbm' to version 1.18.1, an important bugfix release 2018-11-11T15:38:50+00:00 Alexey Dokuchaev danfe@FreeBSD.org 2018-11-11T15:38:50+00:00 936a36e30dd301c382ea294a0e35822d16c879d1 which restores compatibility with old databases (version 1.8) and some later versions which were built without mmap(2) support. Due to shlib version change, bump port revisions of the consumer ports. PR: 233059 Exp-run by: antoine Approved by: maintainer (johans, numerous timeouts)
which restores compatibility with old databases (version 1.8) and some
later versions which were built without mmap(2) support.  Due to shlib
version change, bump port revisions of the consumer ports.

PR:		233059
Exp-run by:	antoine
Approved by:	maintainer (johans, numerous timeouts)
Fix _gdbm module for Python 3 2017-12-29T18:47:42+00:00 Sunpoet Po-Chuan Hsieh sunpoet@FreeBSD.org 2017-12-29T18:47:42+00:00 8c032835b7fa7e2dd6b3a9a1396d7ead32972ab2 - Bump PORTREVISION for package change PR: 223136 Submitted by: Greg V <greg@unrelenting.technology>
- Bump PORTREVISION for package change

PR:		223136
Submitted by:	Greg V <greg@unrelenting.technology>
Convert Python ports to FLAVORS. 2017-11-30T15:50:30+00:00 Mathieu Arnold mat@FreeBSD.org 2017-11-30T15:50:30+00:00 551be3c7231225ed9c26479af2b8914fb2ef0ea8 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
  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