Bug 196340 - Mk/Uses/python.mk: PYTHON_VERSION variable in DEPENDS_ARGS conflicts with and breaks autoconf-based ports
Summary: Mk/Uses/python.mk: PYTHON_VERSION variable in DEPENDS_ARGS conflicts with and...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Many People
Assignee: freebsd-python mailing list
URL:
Keywords: needs-patch, needs-qa
Depends on:
Blocks:
 
Reported: 2014-12-28 22:21 UTC by Antoine Brodin
Modified: 2015-01-02 16:49 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Brodin freebsd_committer 2014-12-28 22:21:35 UTC
In Mk/Uses/python.mk we have:

DEPENDS_ARGS+=          PYTHON_VERSION=${PYTHON_VERSION}
where PYTHON_VERSION is python2.7 or python3.x

But autoconf based ports use PYTHON_VERSION with a different meaning:

  [ax_prog_python_version=`${PYTHON} -c "import sys; sys.stdout.write(sys.version[[:3]])" 2>/dev/null`;
  AC_SUBST(
   [PYTHON_VERSION],
   [$ax_prog_python_version])

so there, PYTHON_VERSION is 2.7 or 3.x

This commit workarounded for devel/py*-gobject3 but other ports are likely affected:

https://svnweb.freebsd.org/changeset/ports/374402
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2014-12-29 02:06:05 UTC
antoine, 

Any considerations and/or suggestions for a renamed variable?
Is this a good time to also introduce a prefixed variable namespace?
Comment 2 Antoine Brodin freebsd_committer 2015-01-02 16:49:18 UTC
(In reply to Kubilay Kocak from comment #1)
> Any considerations and/or suggestions for a renamed variable?

FLAVOR ?  bapt@ is working on something but no ETA as it breaks portupgrade / portmaster