Bug 218672 - ports-mgmt/portlint: false positive "possible direct use of command "python" found" for OPTION_USES statements
Summary: ports-mgmt/portlint: false positive "possible direct use of command "python" ...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Joe Marcus Clarke
URL: http://svnweb.freebsd.org/changeset/p...
Keywords: dogfood
Depends on:
Blocks:
 
Reported: 2017-04-15 05:58 UTC by Gerald Pfeifer
Modified: 2017-04-23 05:07 UTC (History)
1 user (show)

See Also:
koobs: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gerald Pfeifer freebsd_committer freebsd_triage 2017-04-15 05:58:28 UTC 
After recent changes to lang/gcc6 and other ports by miwi (which fixed
an actually problem) I am now seeing

~/ports/lang/gcc6> portlint
WARN: Makefile: [48]: possible direct use of command "python" found.
use ${PYTHON_CMD} instead.

This complains about 
  JAVA_USES=              python shebangfix
where JAVA is one of the OPTIONS of this port and USES=python is one
of the common uses of USES= and in general the OPTION_USES helper.

To fix this, probably best ignore "[[:letter:]]_USES=.*python" for this
warning?
Comment 1 Joe Marcus Clarke freebsd_committer freebsd_triage 2017-04-21 19:52:27 UTC 
Committed to 2.1.7.8.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2017-04-23 05:07:34 UTC 
The SVN post-commit hook (and/or bugzilla commit log parser) obviously did not like the following syntax for multiple PR (issue id) references, so the commit [1] resolving this issue, was not referenced here as a comment:


PR:		218260 [1]
		218325 [2]
		218672 [3]

[1] http://svnweb.freebsd.org/changeset/ports/439128