tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: localize _PYSETUPINSTALLARGS in lang/python/extension.mk and/or _PYSETUPTOOLSINSTALLARGS in egg.mk



On Tue, 23 Apr 2013 20:14:41 +0900, <rodent%netbsd.org@localhost> wrote:

Additionally, this seems wrong:

.if ${_PYTHON_VERSION} == "31" || ${_PYTHON_VERSION} == "32" || ${_PYTHON_VERSION} == 
"33"
DEPENDS+=               
${PYPKGPREFIX}-distribute-[0-9]*:../../devel/py-distribute
.else
DEPENDS+=               
${PYPKGPREFIX}-setuptools>=0.6c9:../../devel/py-setuptools
.endif

That's saying that an egg-aware package using python27, for example, must use
py-setuptools. This is not the case for the latest version of py-nltk, which
is based on py-distribute, but is also egg-aware. NLTK 3.0.x supports python
2.6, 2.7, and python 3.y, which I suppose means that py-distribute can also
work for python27 and python26 (this is also evidenced by not seeing any
restrictions to PYTHON_VERSIONS_ACCEPTED in py-distribute).

Is there some reason we're restricting egg-aware python package to the
py-setuptools method of packaging?

From commit log of lang/python/egg.mk:
revision 1.14
date: 2012/07/25 19:07:49;  author: drochner;  state: Exp;  lines: +6 -1
use py-distribute for Python3 rather than py-setuptools
(The former might be used for Python2 as well, but it needs more
testing.)

--
OBATA Akio / obache%NetBSD.org@localhost


Home | Main Index | Thread Index | Old Index