Created attachment 158443 [details] shar archive
Created attachment 158444 [details] poudriere log
Review: * Use DISTNAME to deprecate GH_PROJECT * Sort USE_PYTHON values * COMMENT, remove leading "Python " * Strip trailing slash from pkg-descr WWW: URL
Additionally: * Use CHEESESHOP unless Github has tests/testsuite * PORTVERSION is 0.1.0 See: https://pypi.python.org/pypi/dnschain/0.1.0
Kubilay, > * Use CHEESESHOP unless Github has tests/testsuite > * PORTVERSION is 0.1.0 See: https://pypi.python.org/pypi/dnschain/0.1.0 But Github is the real upstream for py-dnschain. This OkTurtles guy is the original author. He forgot to set version on python project, so CHEESESHOP just defaulted to 0.1.0. I suggest we should keep Github since it isn't the fork in this case.
(In reply to yuri from comment #4) The issue not strictly about where upstream is, the issues are that: * Users and pip default to using packages provided by PyPi if sdists exist there * PyPi is the canonical/official package library system for Python in general * Other packages that may depend on another python package use PyPi versioning in {*_requires) fields. Regarding distribution files, once naming/versioning issues are addressed: We (Python Team) prefer distribution files and describing python ports from CHEESESHOP and PyPi metadata in the absence of a compelling reason to do otherwise (such as the sdist doesnt contain tests/ or test suite files). A couple of reason for this are: * portscout works with CHEESESHOP by default, and has been known not to work for notifying on github version updates. I believe it still doesn't work * It encourages upstream authors to understand, correctly and accurately package their software. The author should ensure that the PyPI entry has up-to-date and correct metadata, especially versioning and naming. If the __version__ data in the sources are incorrect, they need to be fixed. Alternately if the PyPI version is incorrect, *it* should be fixed. On a related note, X.Y.Z versioning is much easier, so I would encourage you to suggest, and the author to consider standard, simple semantic, versions. All of the above will ensure the minimization of naming and other conflicts for both the FreeBSD Ports framework, its Python users, and other users of the software.
Created attachment 158510 [details] Updated shar
Updated QA log required? (log datestamp < shar datestamp)
QA is passing fine. This port is ready to be committed.
A commit references this bug: Author: amdmi3 Date: Fri Dec 4 15:03:13 UTC 2015 New revision: 402992 URL: https://svnweb.freebsd.org/changeset/ports/402992 Log: Python library for looking up blockchain data via DNSChain WWW: https://github.com/okTurtles/pydnschain PR: 201384 Submitted by: yuri@rawbw.com Changes: head/dns/Makefile head/dns/py-dnschain/ head/dns/py-dnschain/Makefile head/dns/py-dnschain/distinfo head/dns/py-dnschain/pkg-descr