blob: 5da8dd6836e69397c2013a938976edd5384e9e5b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
# $NetBSD: egg.mk,v 1.20 2014/12/31 13:57:28 wiz Exp $
#
# Common logic to handle Python Eggs
#
.include "../../mk/bsd.fast.prefs.mk"
.include "../../lang/python/pyversion.mk"
# This file should be included to package python "distributions" which
# use setuptools to create an egg. Some distributions use distutils,
# which creates an egg-info file; those should use distutils.mk
EGG_NAME?= ${DISTNAME:C/-([^0-9])/_\1/g}
EGG_INFODIR?= ${EGG_NAME}-py${PYVERSSUFFIX}.egg-info
PYDISTUTILSPKG= yes
PY_PATCHPLIST= yes
# True eggs always have an egg-info directory, and thus there is no
# PLIST conditional (as in distutils.mk for old versions of python).
# Note that we substitute EGG_INFODIR rather than EGG_FILE, because
# the egg information in an egg comprises multiple files in an
# egg-info directory.
# The PLIST substitution of EGG_NAME is not necessary. However, it
# is convenient. See lang/ruby/gem.mk and PLIST files for ruby gem
# packages to understand other examples of this feature in non-python
# packages.
PLIST_SUBST+= EGG_NAME=${EGG_NAME}-py${PYVERSSUFFIX}
PLIST_SUBST+= EGG_INFODIR=${EGG_INFODIR}
PRINT_PLIST_AWK+= { gsub(/${EGG_NAME}-py${PYVERSSUFFIX}.egg-info/, \
"$${EGG_INFODIR}") }
PRINT_PLIST_AWK+= { gsub(/${EGG_NAME}-py${PYVERSSUFFIX}-nspkg.pth/, \
"$${EGG_NAME}-nspkg.pth") }
_PYSETUPTOOLSINSTALLARGS= --single-version-externally-managed
.if ${_USE_DESTDIR} == "no"
_PYSETUPTOOLSINSTALLARGS+= --root=/
.endif
DEPENDS+= ${PYPKGPREFIX}-setuptools>=0.8:../../devel/py-setuptools
INSTALLATION_DIRS+= ${PYSITELIB}
.include "../../lang/python/extension.mk"
|
