[Bug 226486] Add USE_PYTHON=app instead of the noflavors option

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 226486
           Summary: Add USE_PYTHON=app instead of the noflavors option
           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: yuri at freebsd.org
                CC: freebsd-ports-bugs at FreeBSD.org

Rationale:
Python ports can be divided into 2 categories: apps and libs. Apps are only
usable through executables, and provide no externally usable python modules.
Everything else is in libs category.

Multiple packages for py2/py3 should always be built for libs. But for apps the
need for separate packages isn't as obvious. It could be argued that they are
needed to provide the user choice between python2 and python3. It could also be
argued that they aren't needed because one package is sufficient since it
provides all needed executables.

Suggestion:
Add USE_PYTHON=app. Ports that are apps should always set USE_PYTHON=app.
Framework (python.mk) then will make a choice what is done: 'app' could trigger
'noflavors', or not. The point is that individual ports will be free of this
choice, and this will not need to be discussed individually for individual
ports.

Additionally, 'concurrent' could be implied when there is no 'app'.

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