Stefan Küng wrote:
> Simon Large wrote:
>
>> Peter Mounce wrote:
>>
>>> Simon Large wrote:
>>>
>>>> I thought Stefan had solved this one before by making a new guid
>>>> automatically for every build, using ??????.???????.??????.????????
>>>> somewhere.
>>>
>>>
>>>
>>>
>>> The package and product GUIDs are indeed randomly generated for each
>>> build. It's the UpgradeCode that has to remain the same. But a
>>> MajorUpgrade does not occur if a.b.c of a.b.c.d of the version number
>>> remains the same - ie, the nightlies. That means nightly users will
>>> get more than one entry in the add/remove programs applet, among
>>> other (also not too serious) things.
>>
>>
>>
>> Silly question, but how was it working before and has stopped working
>> now?
>
>
> It never "stopped working". It has been that way ever since.
> The problem we face is that without changing the third number in the
> version, the MSI won't upgrade files which don't have a version
> information attached to. Since our binaries all have a version resource,
> they get upgraded properly. What won't be upgraded properly are text
> files (e.g. autolist.txt, license files, ...), the apr-iconv dll's (they
> don't have a version resource) and of course the program menu shortcuts.
> But since those don't change for nightly builds anyway, we can safely
> ignore that problem.
So you are saying (contrary to Peter) that we *don't* need to uninstall
the nightly each time? That is good news :-)
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Aug 19 00:55:03 2005