So, distutils makes the script shebang point at the right python during build_scripts and this is happening on your build machine:
running build_scripts
creating build\scripts-2.7
copying and adjusting bzr -> build\scripts-2.7
What, if anything, do you then do to the script files at install time? If nothing, how is the python shebang at the top of script pointing at the right place if I could install ActivePython in a directory of my choosing? And why is the same path in the bat file any more of a problem?
I'm interested in fixing the root problem here, I just don't quite understand your package manager's requirements.
I'm looking at your build log here: pypm-free. activestate. com/2.7/ win32-x86/ pool/b/ bz/bzr- 2.2.0_win32- x86_2.7_ 1.pypm. d/log>
<http://
So, distutils makes the script shebang point at the right python during build_scripts and this is happening on your build machine:
running build_scripts
creating build\scripts-2.7
copying and adjusting bzr -> build\scripts-2.7
What, if anything, do you then do to the script files at install time? If nothing, how is the python shebang at the top of script pointing at the right place if I could install ActivePython in a directory of my choosing? And why is the same path in the bat file any more of a problem?