Date: Tue, 12 Dec 2017 13:36:41 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Sergey Akhmatov <sergey@akhmatov.ru>, freebsd-python@freebsd.org, freebsd-ports@freebsd.org Subject: Re: What is the preferred MASTER_SITES for python port? Message-ID: <e9b33755-b196-0441-bfa0-1a565a566a8f@FreeBSD.org> In-Reply-To: <56059f84-ab05-9db5-13d4-b1a443df0832@akhmatov.ru> References: <56059f84-ab05-9db5-13d4-b1a443df0832@akhmatov.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/12/2017 1:28 am, Sergey Akhmatov wrote: > Hello. > > Suppose I want to port some python package that exists in the Python > Package Index (PyPI) and has it's source code available on some official > website or github. > > Is there any policy or recommended practice for choosing MASTER_SITES? > Should I use "USE_GITHUB=yes" or "MASTER_SITES= CHEESESHOP" for such > package? > > I've looked for the answer in Porters Handbook and at > https://wiki.freebsd.org/Python/PortsPolicy but haven't found it. > > Thank you. > Hi Sergey: Use CHEESESHOP by default unless there is a compelling (temporary) case not to. Examples include certain files are not correctly packaged/included in the PyPI sdist, such as test suite/files/data. In these cases, use the alternative MASTER_SITES, open issues/PR's upstream to get them included, and switch to CHEESESHOP when it lands. This ensures an upstreams packaging/deployment pipeline is well tested and standardised, as it is heavily relied upon (setuptools, autoplist, documentation, discoverability, etc) Note: Irrespective of MASTER_SITES, if a package is in PyPI it *must* be named exactly by its <pypi-name>. That is: * SVN Directory: py-<pypi-name> * PORTNAME= <pypi-name> * PKGNAMEPREFIX=${PYTHON_PKGNAMEPREFIX} ./koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e9b33755-b196-0441-bfa0-1a565a566a8f>