On Fri, Jan 16, 2009 at 2:50 PM, Peer Sommerlund
<[email protected]>wrote:
> 2009/1/15 TK Soh <[email protected]>
>
>> On Thu, Jan 15, 2009 at 11:55 AM, Peer Sommerlund
>> <[email protected]> wrote:
>> > The solution is simple: The installer should call the uninstaller as the
>> > first step if it detects an installed THG.
>>
>> I am open for patches.
>>
>
> I have some trouble with my patchbomb, so attached is a patch file.
>
> I'm not quite satisfied with the workflow, so maybe somebody can come up
> with a better way to do it.
>
> Also, the patch is relative to installer/tortoisehg.iss but the MQ bundle
> process patches HG .iss so the patch should probably be moved somewhere
> else.
>
>
If/when we switch over to the forest approach, I would prefer to check in
our installer files either into the forest repo or into TortoiseHg itself
under contrib/win32 where they can be cleanly merged. I would like to get
rid of as many patches out of the patch queue as possible so changes to
these files can be tracked more sanely.
(installer files = mercurial.ini, mercurial.iss, ReadMe.txt, plink, kdiff3,
icons, etc)
--
Steve
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
