Right now, it's not possible to call some of the distutils-r1 phase functions more than once. In particular, the setup tasks performed by distutils-r1_python_compile are not suitable for calling multiple times. Any thoughts how we could handle this cleanly? How should we support multiple impls?
If someone is going to call distutils-r1_src_{compile,install} more than once, the cleanest thing would be to have a separate build directory for each instance. I think the most common usage for this would be multiple python projects in the same package. To solve that case, we could set BUILD_DIR based on the current working directory. To illustrate: : EPYTHON=python2.7 : PWD=${WORKDIR}/foo-1.2.2/project1 BUILD_DIR=${WORKDIR}/build-python2.7/foo-1.2.2/project1 : EPYTHON=python3.3 : PWD=${WORKDIR}/${P}/project2 BUILD_DIR=${WORKDIR}/build-python3.3/foo-1.2.2/project2 The actual BUILD_DIR assignment would be this: BUILD_DIR=${WORKDIR}/build-${EPYTHON}/${PWD#${WORKDIR}}
Sounds reasonable. What about pydistutils.cfg? Should we place it (and therefore $HOME) inside $BUILD_DIR? Or maybe we should re-create that file in every phase?
Seems nobody came up with a real need for this so far.
