[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Upgrading + Verson numbering

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-08-18 22:53:47 CEST

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.

And of course, for official releases where the third number in the
version changes there isn't a problem at all.


   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 Thu Aug 18 22:54:08 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.