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

Re: Installer woes

From: Joseph Galbraith <galb_at_vandyke.com>
Date: 2005-10-19 16:59:10 CEST

Simon Large wrote:
> pete@molehole.org wrote:
>> On Wed, Oct 19, 2005 at 11:10:43AM +0200, Molle Bestefich wrote:
>>> real version --> installer version:
> >> --> 1.2.45432,
>>> --> 1.3.07654 etc.
>> This scheme would get my vote. I would rather have the build number
>> than the micro version number, and have cursed MSI in the past for
>> not allowing both...
> -1. I think you need *either* build number *or* minor version (and I
> prefer build number).
> Remember that in about 2 years time, maybe less, TSVN's build will gain
> another digit as r9999 rolls over to r10000.
> To accommodate both in the scheme above you would need:
> --> 1.2.405432
> --> 1.2.1007654
> Do you really want numbers that long?

If I read my MSI docs correctly, it is worse than that.

> major.minor.build
> The first field is the major version and has a maximum value
> of 255. The second field is the minor version and has a
> maximum value of 255. The third field is called the build
> version or the update version and has a maximum value of
> 65,535.

So we have to make sure whatever we do doesn't overflow this



PS. The version information also has some limitations along these
lines for file version and product version. Each of these values
is a 64 bit value. If I remember correctly, the 64-bit value
is split into 4 16 bit values, for each of

So 65,535 is the limit for build number in the version resources too.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 19 16:50:24 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.