[erlang-questions] Version numbering scheme change and the implication / Re: [ANN] Erlang/OTP 17.0-rc1 has been released.

[Fred Hebert]

Always be wary of these macros, because custom releases set by users can
pick and match versions of applications from multiple releases and build
a new release to develop from, and then spin off more and more releases.

In this case, the macros are suddenly worthless or not representative of
the true dependency you are expressing -- the one on individual
application versions within an OTP release.

On 02/07, Motiejus Jakštys wrote:
> 2014.02.07 12:20, Andreas Schumacher rašė:
> > 
> > The OTP major release and the complete OTP version can be retrieved from
> > erlang code using the following:
> > 
> >    1> erlang:system_info(otp_release).
> >    "17"
> >    2> erlang:system_info(otp_correction_package).
> >    "17.0-rc1"
> > 
> > NOTE: The name of the argument "otp_correction_package" will be changed
> > to "otp_version." In addition, a corresponding flag "otp_version" will
> > be added to the erl command, in order to allow the extraction of the
> > complete version number from command line tools.
> 
> Any plans to support ?OTP_RELEASE and ?OTP_VERSION?
> 
> This would give us ability to portably* create portable applications.
> 
> Regards,
> Motiejus
> 
> [*]: now these constants are set by build system (rebar, Makefiles).
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions