A module for parsing versions (PEP-440)

[Totktonada]

Authors of external tarantool modules often need to determine a version of tarantool either to enable/disable some functionality or for the sake of conditional testing. It is easy to obtain the version string, but splitting to components is implemented in modules again and again.

Examples of tarantool version parsing code:

• tarantool-php (in tests) (needs update for 2.10+)
• tuple-keydef (in tests) (needs update for 2.10+)
• crud (in sources)
• crud (in tests)
• cartridge-cli (in sources)
• vshard (in sources)

I propose to extend the problem and implement a general version parsing code in tarantool. In particular, it should be applicable for parsing of tarantool's version.

Materials to dive into the topic:

• Semantic Versioning
• PEP-440 ('Version Identification and Dependency Specification') and pkg_resources.parse_version()
• Debian Policy (see also comments in mkrepo)
• Fedora Versioning Guidelines
• Version tokens and parsers in brew
• EAPI-7 functions for version manipulations in Gentoo

[ligurio]

BTW, there is a separate library libversion that compares version in different formats.