pete@molehole.org wrote:
> On Wed, Oct 19, 2005 at 08:59:10AM -0600, Joseph Galbraith wrote:
>> 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
>> value.
>
> I remember. However, a) in 2.5 years we've had 4.5k revisions, so assuming linear progression, that's a significant number of years before we hit that limit, and b) if we hit that limit, we can surely just increment the major or minor version number and add some code to subtract 65536 from the build number at that point, and still have it turn out ok...?
>
> I would expect the limits to change once MSI gets ported to 64 bit...?
I doubt it... I don't think the on-disk structures have changed
for 64 bit... so the limits are the same.
> Whatever; Not My Problem For A While Yet (tm) ;-)
Nope... not for a while-- ~36 yrs is a long time :-)
(But it becomes drastically shorter if you try to combine
other information into the field.)
Thanks,
Joseph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 19 17:28:14 2005