[erlang-questions] OTP Version

Michael Truog mjtruog@REDACTED
Fri Jul 18 00:43:07 CEST 2014

On 07/17/2014 02:21 PM, Fred Hebert wrote:
> On 07/17, Tristan Sloughter wrote:
>> If for all OTP 17.x.y the runtime is going to consider it 17:
>> 1> erlang:system_info(otp_release).
>> "17"
> For reverence, the new method to get the version according to the docs
> is: http://www.erlang.org/doc/system_principles/versions.html
>      In an OTP source code tree, the OTP version can be read from the text
>      file <OTP source root>/OTP_VERSION. The absolute path to the file can be
>      constructed by calling filename:join([code:root_dir(), "OTP_VERSION"]).
>      In an installed OTP development system, the OTP version can be read from
>      the text file <OTP installation root>/releases/<OTP release
>      number>/OTP_VERSION. The absolute path to the file can by constructed by
>      calling filename:join([code:root_dir(), "releases",
>      erlang:system_info(otp_release), "OTP_VERSION"]).
> Do note that the version number can be followed by '**', meaning it was
> patched with otp_patch_apply.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
So, the idea is that only the source code has a version.  The binary installation has no minor or release version, unless you check individual erlang applications.  The reason given so far (http://erlang.org/pipermail/erlang-questions/2014-April/078590.html), is it is too hard to provide the minor and release version because different installations are likely to use different source tree dependencies at different versions, so we are likely to lose any dependable information about what version set of erlang applications are most stable together.

More information about the erlang-questions mailing list