No, there's not any problem with the packaged KDiff3 binary that I'm aware of. The conversation started when I listed components that are out of date in TortoiseHg (the first post in November).
I'm not sure what "simolicity" is. Did you mean simplicity? I assumed that KDiff3 was customized in TortoiseHg. But since it's not, wouldn't it work to just copy the KDiff3 EXE from the KDiff3 installer? As you said, the KDiff3 shell extension shouldn't be included with TortoiseHg, but it doesn't need to be if just the EXE was copied. That would seem to me to be the simplest way to bundle KDiff3, and I would think it would take only a few minutes. Also, it wouldn't need to be done every time a release of TortoiseHg is made, but only when KDiff3 is updated. Another possibility would be if flags can be passed to the KDiff3 installer to tell it to not install the shell extension. As a programmer myself, I can look into this further if you'd like. -- Timothy ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
