For python modules not using MODPY_SETUPTOOLS, the installed .pyc
files refer to their source .py files in the fake directory instead of
LOCALBASE. I am not sure how bad it is in general, but this is at
least a problem for some py-twisted regress tests which fails because
of this.
I see no reason why it should not be handled correctly as in the
"MODPY_SETUPTOOLS=Yes" case.
Comments?
Index: python.port.mk
===================================================================
RCS file: /cvs/ports/lang/python/python.port.mk,v
retrieving revision 1.24
diff -u -r1.24 python.port.mk
--- python.port.mk 27 Oct 2008 00:02:27 -0000 1.24
+++ python.port.mk 7 Dec 2008 09:35:16 -0000
@@ -53,7 +53,8 @@
--root=${DESTDIR} \
--single-version-externally-managed
.else
-MODPY_DISTUTILS_INSTALL?= install --prefix=${PREFIX}
+MODPY_DISTUTILS_INSTALL?= install --prefix=${LOCALBASE} \
+ --root=${DESTDIR}
.endif
MAKE_ENV+= CC=${CC}
