On Sat, Mar 5, 2011 at 5:31 AM, Peer Sommerlund <[email protected]> wrote: > On 4 March 2011 17:03, Steve Borho <[email protected]> wrote: >> On Fri, Mar 4, 2011 at 8:23 AM, Stanimir Stamenkov <[email protected]> >> wrote: >>> Using the TortoiseHg 2.0 version on Windows I've noticed the PATH is >>> added with "<TortoiseHg>\bin" directory containing "hg.cmd" and >>> "thg.cmd" shell scripts invoking "hg.exe" and "thg.exe" from the >>> parent <TortoiseHg> directory. What's the reason the *.exe files >>> are not directly invoked/included in the PATH? I'm asking because >>> using the given setup breaks existing shell scripts (batch files) >>> invoking 'hg' in succession - one has to account 'hg' is a batch >>> file and modify the invoking script as: >>> >>> call hg ... >>> call hg ... >> >> py2exe does not support --bundle 3 for x64 architectures, so it is >> unable to store any of the pyd or DLL files in the library.zip file. >> To avoid adding about 2 dozen DLLs to the system path, I introduced >> the bin/ folder. >> >> This has got to be the default installer behavior. > > ... until somebody adds support for --bundle 3 for x64 architectures to > py2exe.
It's been a known issue for several years, I'm not holding my breath. -- Steve Borho ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
