Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Jul 2015 08:39:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 201384] [NEW PORT] dns/py-dnschain: Python library for looking up blockchain data via DNSChain
Message-ID:  <bug-201384-13-4aX1ePShbe@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201384-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-201384-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201384

--- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201384-13-4aX1ePShbe>