[Bf-committers] Why was BLENDER_VERSION_CHAR cleared?

[Bastien Montagne]

Maybe I’m wrong, but imho the package creation system should rather use 
the BLENDER_SUBVERSION number (currently 4, we are in 2.60.4), rather 
than BLENDER_VERSION_CHAR...

Le 14/11/2011 17:18, IRIE Shinsuke a écrit :
> Thanks for the recommit.
>
> Of course the build scripts use the svn revision, but also have to use
> the version character like "2.60.1+svn41828", where ".1" is translated
> from "a".
>
> For example, most package systems compare the versions as:
>
>     2.60<  2.60+svn41834<  2.60.1<  2.60.1+svn41834<  2.60.2<  2.61
>
> If we use "2.60+svn41834" for svn snapshot after 2.60a, the package
> system incorrectly downgrade it to "2.60.1" (= 2.60a).
>
>> Recommited "a".
>> Although I think this is wrong, this is only intended for a release.
>> If you want to make svn snapshot packages you should use the svn revision.
>>
>> Am 14.11.2011 14:30, schrieb IRIE Shinsuke:
>>> When BLENDER_VERSION_CYCLE was changed to beta (r41802),
>>> BLENDER_VERSION_CHAR also was reset to blank. As the result, build
>>> scripts like build_files/package_spec/build_debian.sh recognize the
>>> Blender's version as 2.60, which is less than 2.60a, and the
>>> version-down confuses the package system so that the newer version
>>> becomes not installable.
>>>
>>> Please keep BLENDER_VERSION_CHAR until 2.61 release!
>>>
>>> --
>>> IRIE Shinsuke
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>