"batteries included"-installer, was: NullSoft installer for Mercurial

[Steve Borho]

On Thu, 2007-09-06 at 08:34 +0200, Jens.Wulf at sew-eurodrive.de wrote:
> Hi Steve,
> 
> > PS2: I'm still waiting for more feedback on the "batteries included" installer. 
> > If anyone is actually using it :) , please let me know where it needs to be improved. 
> 
> I just tried your "batteries included"-installer and I am glad to have "hg view" and "hg vdiff" now. Maybe I will get used to "hg qct", too (which I don't use at home/linux).
> I did not install to "C:\program files\mercurial" and broke "hg view" by doing so, as there are absolute paths in 
> 	mercurial.ini
> 	scripts/hgk.cmd
> So I had to edit those files. I think this is not too bad with mercurial.ini (as it is global and overriden by my local one anyway), but one should not have to touch scripts/hgk.cmd.

I just added an 'AfterInstall' script to do a string replace on the INI
file and the shell scripts to insert the actual install location into
those files.  It'll be in the next snapshot I release.  Unfortunately
this can break those cases where Mercurial doesn't deal well with spaces
in the command paths (thinking of [ui] ssh, specifically).  I need to
find a way to make Inno Setup generate safe paths.

> Regarding your installer philosophy questions: generally I like the modular/linux approach which allows to install (mostly static) things like tcl/tk from distribution packages and evolving software (like hg) from source. But as I often feel that this is not as easy on windows I opted for "batteries included". Furthermore, your modular installer description lists some outstanding issues.

Well, the all-in-one installer should probably have a similar issues
list, I'm just unaware of most of them :)

Thanks for the bug report.

-- 
Steve Borho (steve at borho.org)
http://www.borho.org/~steve/steve.asc
Key fingerprint = 2D08 E7CF B624 624C DE1F  E2E4 B0C2 5292 F2C6 2C8C