forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cyriaque Dupoirieux <Cyriaque.Dupoiri...@pcotech.fr>
Subject Re: svn commit: r375238 - /forrest/trunk/tools/forrestbar/xpi/install.rdf
Date Mon, 06 Feb 2006 11:47:41 GMT
Ross Gardler a écrit :
> cdupoirieux@apache.org wrote:
>> Author: cdupoirieux
>> Date: Mon Feb  6 02:23:36 2006
>> New Revision: 375238
>>
>> URL: http://svn.apache.org/viewcvs?rev=375238&view=rev
>> Log:
>> Update the max Firefox version to 1.5.0.1...
>> (I don't put 1.6 or other version because the Mozilla road map is not 
>> up-to-date ...)
>>
>> Modified:
>>     forrest/trunk/tools/forrestbar/xpi/install.rdf
>>
>> Modified: forrest/trunk/tools/forrestbar/xpi/install.rdf
>> URL: 
>> http://svn.apache.org/viewcvs/forrest/trunk/tools/forrestbar/xpi/install.rdf?rev=375238&r1=375237&r2=375238&view=diff

>>
>> ============================================================================== 
>>
>> --- forrest/trunk/tools/forrestbar/xpi/install.rdf (original)
>> +++ forrest/trunk/tools/forrestbar/xpi/install.rdf Mon Feb  6 
>> 02:23:36 2006
>> @@ -31,7 +31,7 @@
>>        <Description>
>>          <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
>>          <em:minVersion>0.9</em:minVersion>
>> -        <em:maxVersion>1.5</em:maxVersion>
>> +        <em:maxVersion>1.5.0.1</em:maxVersion>
>
> Wow, that is easy ;-)
>
> All devs take not of this commit, it will come up reasonably frequently.
>
> I wonder if it is possible to do something like:
>
> <em:maxVersion>1.5.*</em:maxVersion>
Yes it seems that it is possible, I have found this in the 
developer.mozilla.org site :
------------------------------------------------------------------------


    Version format

A *version string* consists of one or more /version parts/, separated 
with dots.

Each *version part* is itself parsed as a sequence of four parts: 
<number-a><string-b><number-c><string-d>. Each of the parts is optional.

Numbers are integers base 10 (may be negative), strings are ASCII.

A few examples of valid version parts:

    * 0 (as in 1.0): <number-a>=0
    * 5a (as in 1.5a): <number-a>=5, <string-b>=a
    * 5pre4 (as in 3.5pre4): <number-a>=5, <string-b>=pre, <number-c>=4
    * * (as in 1.0.*): <string-b>=*

A few special parsing rules are applied for backwards compatibility and 
readability:

    * if the version part is a single asterix, it is interpreted as an
      infinitely-large number:
      1.5.0.* is the same as 1.5.0./(infinity)/
    * if string-b is a plus sign, number-a is incremented to be
      compatible with the Firefox 1.0.x version format:
      1.0+ is the same as 1.1pre

The rationale behind splitting a version part into a sequence of strings 
and numbers is that when comparing version parts, the numeric parts are 
compared as numbers, e.g. '1.0pre1' < '1.0pre10', while the strings are 
compared bytewise. See the next section for details on how versions are 
compared.

------------------------------------------------------------------------


We can either put 1.5+ or 1.5.*

Don't know what is best.

Cyriaque,


>
> Ross
>
>

Mime
View raw message