On Fri, Feb 13, 2009 at 1:22 AM, Steve Borho <[email protected]> wrote:
> On Thu, 2009-02-12 at 20:22 +0100, Peer Sommerlund wrote:
>>
>>
>> 2009/2/12 TK Soh <[email protected]>
>>         On Thu, Feb 12, 2009 at 2:56 AM, Steve Borho <[email protected]>
>>         wrote:
>>         > In theory, a future upgrade of THG would only require a
>>         restart of
>>         > explorer.exe if the upgrade were 'in place'.
>>
>>
>>         Technically, restart explorer.exe is all we need (rebooting is
>>         a
>>         simply the easiest way to guarantee that). I heard TCVS is
>>         doing this,
>>         but not sure how complicated the approach is.
>>
>>         If we can get the WIX installer in place, then many things
>>         should be possible.
>>
>>
>>
>>
>> It is surprising how much stuff you can do from Inno.
>>
>>
>>
>> I did some work on Wix about a year ago. As I recall My final
>> conclusion was that the install-without-reboot is probably not worth
>> the work needed to convert from Inno, since Inno just requires a small
>> program (maybe 10 lines of code) that restarts explorer. As the
>> installer write in HKLM we must reboot no matter which installer we
>> use.
>>
>>
>> To completely avoid reboot we should add a user-only installation
>> path.
>>
>>
>> There are other arguments for a switch to Wix, e.g. msi being a
>> windows standard. On the other hand, after scanning the manuals of
>> both products my impression was they can do almost the same things,
>> and that wix files are significantly more complex to read. Wix does
>> not give you flexibility for free, you will also have to write custom
>> code to make a customized installer - and in my eyes this reduces the
>> advantage of wix.
>>
>> I would not pretend to have deep knowledge about writing windows
>> installers, so maybe somebody could explan the advantage of switching
>> to wix.
>
> Wix seems to support optional install parameters better than Inno does,
> but that may just be lack of experience on my part.  Here's what I'd
> like to see in the 0.8 installer:
>
> * Optional overlay support   (no TortoiseOverlays or hooks registered)

Do you mean no display of overlays icons, or display without using
TortoiseOverlays?

> * Optional shell integration (no COM services registered at all)

Just to speak my mind. While I understand the 'issues' this is trying
to address, we can't call it a Tortoise(HG) without the shell
integration. That's the reason why I never try to provide a channel to
achieve this from within TortoiseHg (yes, it can be done)

I understand the overlay icons display is less than optimum now, but
the context menu has to be there.

> * Detect situations where uninstall is required and force them
>
> For translations, I think we can ship them all.  And I'm not too
> concerned about translating the installer itself, but it would be
> nice.
>
> MSI seems to be the "future" for software distribution on Windows, but
> if we can get the above features without WIX, I would be ok with it.
>
> --
> Steve
>
>

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to