* Stefano Rivera <[email protected]> [20110330 00:30]: > It's caused by the python2.5 install happening before the 2.6 one, and > the 2.6 one doesn't replace the hg script from the 2.5 install. (It > would if we supplied --force)
Mercurial's Makefile always uses --force for this and a few other reaons, but ... > - 'install_scripts': hginstallscripts} > +# Disabled on Debian. We install into the public namespace and don't need > +# to hack sys.path. > +# 'install_scripts': hginstallscripts} ... with the comment this looks good, too. Maybe it would be good to change hginstallscripts upstream so it doesn't do @LIBDIR@ magic if this would be in the public namespace? How can this be detected in a reliable way? Regards, Thomas -- [email protected] - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
