On Fri, Feb 26, 2010 at 12:47 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 26.02.2010 10:54, Adrian Buehlmann wrote:
>
>>>
>>> Also, what you call a "functional msi" might work on your system with
>>> your specific version of the windows installer. Someone using another
>>> version of the windows installer might get another result or the
>>> installation won't work at all.
>>
>> We will ship exactly that in TortoiseHg 1.0, in a couple of days
>> (an msi having both 32 and 64 bit components).
>>
>> But of course without the TortoiseOverlays x86 in our x64 installer, due to
>> the component GUID conflict. We will request our users to download and install
>> TortoiseOveralys x86 themselves for x64 platforms if they want to have
>> overlay icons in 32 bit processes (tested, works fine, but of course is
>> clumsy), citing the GUID conflict.
>>
>> I admit I haven't tested yet on Win XP x64 but on clean Vista x64 SP2 and
>> Windows 7 x64 all this works fine.
>
> I wouldn't be so sure about that. Do an install but with a full log. You
> might be surprised about what doesn't work.
> Please read this post about the problems:
> http://blogs.msdn.com/heaths/archive/2008/01/15/different-packages-are-required-for-different-processor-architectures.aspx
>
>> Per my own cluelessness, it is hard to understand that two packages can't be
>> installed in a single installer, but they work fine once installed, if a user
>> installs these separate packages manually, one after the other.
>>
>> Our minimum required platform will be Win XP and our focus for x64 platforms
>> is clearly Vista and Windows 7. I might as well consider having the x64 installer
>> refusing to install TortoiseHg 1.0 on Win XP x64 if it turns out to be problem on
>> that platform.
>
> The problem(s) are due to the redirections in place, independent of OS
> versions.
>
>> For those interested: 1.0 betas for testing are available on
>> http://bitbucket.org/tortoisehg/thg-winbuild/downloads/
>> (take a tortoisehg-stable-*.msi)
>
>> I still don't see why the exact same component GUID must be used twice
>> in two different products (one being an x86 and the other a x64).
>>
>> Can you explain why it is not possible to have *different* GUIDs?
>>
>> Stupid question (as often): Why not doing something like:
>
> Actually, I fixed it a better way (check the diff and you'll know what I
> mean :) ).
>
> The new version (1.0.13) is online.
Excellent. Thank you very much.
--
Steve Borho
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2452691
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-26 21:09:36 CET