[Bug 216479] Uses/python.mk: specifying USES=python3.3+ and USE_PYTHON=concurrent doesn't produce any ports with USE_DEFAULT_LINKS

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Jan 26 05:58:39 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216479

            Bug ID: 216479
           Summary: Uses/python.mk: specifying USES=python3.3+ and
                    USE_PYTHON=concurrent doesn't produce any ports with
                    USE_DEFAULT_LINKS
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr at FreeBSD.org
          Reporter: dbn at FreeBSD.org
                CC: freebsd-ports-bugs at FreeBSD.org

If a port is python 3 only, and it specifies 'concurrent' then all scripts
installed into $PREFIX/bin will have a suffix.  Since python defaults to
version 2 no port ever gets a script without a suffix.  

However, some ports are split in two: a python2 and a python3 version.  In this
case the latter port is correctly handled.  

I can suggest either (or both):
 1) Adding another flag to indicate with version of python the
USE_DEFAULT_LINKS should be applied, or
 2) Dynamically detecting that a port only supports a specific major version of
python, then specify USE_DEFAULT_LINKS for the default python version for the
port's supported major version.  This will exclude ports who's directory name
does not start with 'py-'.

I suggest both approaches.  

The affected ports appear to be:
# find . -name Makefile | xargs grep USE_PYTHON | grep concurrent | cut -f 1 -d
: | xargs grep USES | grep python:3 | cut -f 1 -d : | sed -e 's|/Makefile||g'
-e 's|\./||g'
sysutils/py-diffoscope
ports-mgmt/py-skog
(false positives)
devel/py3-babel
devel/py3-Jinja2
textproc/py3-pager
textproc/py3-MarkupSafe
textproc/py3-chardet

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-ports-bugs mailing list