Joey Hess wrote: > Bernd, did you get it backwards when writing the above code? > > Build order does not actually matter, but installation order does. > At least in this case, the last python version to run the install > overwrites the script from the other version, so default should be last.
Normally the scripts are not copied a second time, if they exist at the destination (have a look at winpdb, for example - if you want to build it in a chroot, don't forget to s/python/python-all/ in the build-deps. So usually - and in my experience - dh does the right thing as it is now. The last time we had such an issue it was due to the setup.py doing weird things (like creating the to-be-installed script on the fly). I didn't have the time to investigate in zhone, but I'm kinda sure its an issue with its setup.py. -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
