1. 06 Jul, 2018 1 commit
  2. 18 Apr, 2018 2 commits
  3. 28 Feb, 2018 1 commit
  4. 26 Feb, 2018 1 commit
  5. 15 Feb, 2018 1 commit
  6. 06 Feb, 2018 1 commit
  7. 25 Jan, 2018 1 commit
  8. 22 Jan, 2018 1 commit
  9. 21 Jan, 2018 1 commit
  10. 19 Dec, 2017 1 commit
    • mat's avatar
      Enhance USES=uniquefiles to be more generic. · e2e0f973
      mat authored
      This allows to have more complex renaming schemes.  Until now, it could
      only add a prefix or a suffix, but this was not working at all for man
      pages, because it would give man/man1/pyfoo.1.gz-2.7 or
      man/man1/pyfoo-1-2.7.gz.  With this change, a man page will be correctly
      renamed to man/man1/pyfoo-2.7.1.gz.
      Unfix ports that were already handling man pages.
      PR:		220214
      Submitted by:	Fukang Chen (previous patch)
      Exp-run by:	antoine
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D13444
  11. 14 Dec, 2017 1 commit
    • mat's avatar
      Rework PY_FLAVOR to always work. · 7454e855
      mat authored
      Before this, it could have been set to the current flavor of the port
      that may not have been related to Python at all.
      This of course never came up during development because at that time,
      the only flavors were the Python flavors.
      Reported by:	dbn
      Sponsored by:	Absolight
  12. 12 Dec, 2017 2 commits
  13. 11 Dec, 2017 1 commit
    • mat's avatar
      Make USE_PYTHON=concurrent flavors friendly. · 1ac28698
      mat authored
      Before, it would only create the default symlink if the Python version
      was the default Python version.  Change that to if the Python flavor is
      the default flavor.
      PR:		224242
      Sponsored by:	Absolight
  14. 04 Dec, 2017 7 commits
  15. 03 Dec, 2017 1 commit
    • amdmi3's avatar
      Fix default python flavor wrt python version · d0283676
      amdmi3 authored
      There's a flaw in FLAVOR selection logic which makes python FLAVOR
      default to py27 even with DEFAULT_VERSIONS=python=3.6. Fix this and
      (in that order) similar to how it's done in other parts of python.mk.
      This does not affect FLAVOR in default setup (py27 remains), but
      if python default version is modified, it will now properly affect FLAVOR.
      Approved by:	portmgr (antoine)
      Differential Revision:	D13326
  16. 30 Nov, 2017 1 commit
    • mat's avatar
      Convert Python ports to FLAVORS. · 32512cab
      mat authored
        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
  17. 03 Sep, 2017 1 commit
  18. 17 Jun, 2017 1 commit
    • bdrewery's avatar
      Specifying an invalid PYTHON_VERSION against its USES should be IGNORED. · 8c8bacb3
      bdrewery authored
      The port's own USES may note that is only supports certain versions.  If it
      is attempted to build an unsupported version there's no reason to even
      try.  Rather than giving a WARNING, actually mark it IGNORE.
      Currently this should only impact devel/py3-enum34 which does not support
      the default python3 version of 3.6.
      With hat:	portmgr
  19. 06 Jun, 2017 1 commit
  20. 21 Apr, 2017 1 commit
  21. 16 Mar, 2017 1 commit
  22. 07 Jan, 2017 1 commit
    • sunpoet's avatar
      Add more PLIST_SUB to Mk/Uses/python.mk · 23c52b64
      sunpoet authored
      - Add PYTHON2 and PYTHON3
      - Respect PYTHON_VERSION
      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
  23. 25 Dec, 2016 1 commit
  24. 14 Oct, 2016 1 commit
  25. 03 Aug, 2016 1 commit
  26. 25 Jun, 2016 1 commit
  27. 28 Apr, 2016 1 commit
  28. 22 Apr, 2016 1 commit
  29. 14 Apr, 2016 1 commit
  30. 27 Mar, 2016 1 commit
  31. 19 Feb, 2016 1 commit
    • bdrewery's avatar
      For PYTHON_NO_DEPENDS don't pass PYTHON_VERSION to dependencies. · 870062dc
      bdrewery authored
      The PYTHON_NO_DEPENDS only really makes sense in meta ports, where passing
      the PYTHON_VERSION doesn't make sense.  The ports listed will pick up
      USES+=python and the default version as needed.
      This fixes depending on both lang/python2 and lang/python3 in a meta package.
  32. 02 Feb, 2016 1 commit