Bug 213879

Summary: devel/py-tox: Remove argparse RUN_DEPENDS (scheduled for removal)
Product: Ports & Packages Reporter: Li-Wen Hsu <lwhsu>
Component: Individual Port(s)Assignee: Li-Wen Hsu <lwhsu>
Status: Closed FIXED    
Severity: Affects Only Me CC: koobs
Priority: --- Keywords: patch
Version: LatestFlags: koobs: maintainer-feedback+
Hardware: Any   
OS: Any   
Attachments:
Description Flags
py-tox.patch koobs: maintainer-approval+

Description Li-Wen Hsu freebsd_committer freebsd_triage 2016-10-29 13:16:31 UTC
Created attachment 176271 [details]
py-tox.patch

- Remove depending on argparse, all Python versions in ports tree have it as built-in
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2016-10-29 13:20:13 UTC
I understand the motiviation for this change, but I strongly prefer to keep ports I maintain as declarative (and explicit) reflections of their respective upstream packages.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2016-10-29 13:21:14 UTC
Per comment 1 (declarative and explicit), this would includes versions set in USES=python:<version-spec> to match as closely as possible, the upstream version compatibility.
Comment 3 Li-Wen Hsu freebsd_committer freebsd_triage 2016-10-29 13:41:53 UTC
(In reply to Kubilay Kocak from comment #2)
but, I'm going to remove devel/py-argparse, will it be a problem if we still have these lines after removal?
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2016-10-29 13:50:52 UTC
(In reply to Li-Wen Hsu from comment #3)

Yes unfortunately, since most RUN_DEPENDS these days refer to package names and not files (PYTHON_SITELIBDIR/foo/bar.py), which by itself is not a bad thing.

Otherwise, it would only be an issue for users after argparse removal *and* who have a python port installed that is not in the base ports tree, since ports would not 'find' the file that was needed, and the build would stop. The user could then pip install argparse, and then the port could be built.

Having said that (for reference), I agree that in the absence of a global/standard method to allow for builds to work after a port is removed such as mentioned above, the reference should be removed.

I shed a tear today for declarative python ports.

Over to you Li-Wen
Comment 5 commit-hook freebsd_committer freebsd_triage 2016-10-29 17:37:32 UTC
A commit references this bug:

Author: lwhsu
Date: Sat Oct 29 17:37:24 UTC 2016
New revision: 424923
URL: https://svnweb.freebsd.org/changeset/ports/424923

Log:
  - Remove depending on argparse, all Python versions in ports tree have it as
    built-in

  PR:		213879
  Submitted by:	lwhsu
  Approved by:	koobs (maintainer)

Changes:
  head/devel/py-tox/Makefile