* addon: script.module.protobuf
* version: 2.4.1.1
* url: git://github.com/vially/xbmc-protobuf.git
* tag: 2.4.1.1
* xbmc version: eden
I'm not sure I've used the right version number for this release. The
upstream version for protobuf is still 2.4.1 but I had to do some changes
to increase compatibility with XBMC so I've bumped the version number from
2.4.1 to 2.4.1.1
I have tried to find some documentation about the versioning scheme that
XBMC add-ons are using but I couldn't find any. I'm particulary interested
in the way the version is being parsed and compared.
For example which one of these is considered to be the newer version (I'm
not sure whether all of them are considered legal either):
0.1.0 vs 0.1.0-alpha1
0.1.0 vs 0.1.0-1
0.1.0 vs 0.1.0.1
Also, in my particular case, what would happen if a new version was
released upstream with the version number: 2.4.1.1?
Sorry for all the questions but since I've submitted a couple add-ons to
the official repository I just want to make sure I understand how this
versioning works.
Cheers,
Valentin
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Xbmc-addons mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbmc-addons
