env with erlang version number - rebar3, maybe?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

env with erlang version number - rebar3, maybe?

Bartłomiej Górny
Hello

Is it possible to automatically set an env variable with erlang version
number, to solve that notorious deprecaction vs backward compatibility
problem? Rebar3 "knows" major release number (since it supports
"require_otp_vsn" clause), is there a way to set it in the environment?

BG


--
mężczyzna potrzebuje dwóch narzędzi - taśmy klejącej i WD40. co się
rusza, a nie powinno skleić taśmą, a co się nie rusza, a powinno -
spryskać WD40.

(mafodope, bash.org.pl)
_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: env with erlang version number - rebar3, maybe?

Peti Gömöri-2
hello,

since OTP 21 there is a predefined macro OTP_RELEASE that even the Erlang compiler knows (so not rebar3 specific), see http://erlang.org/doc/reference_manual/macros.html#predefined-macros

On Wed, Aug 29, 2018 at 11:18 AM, Bartłomiej Górny <[hidden email]> wrote:
Hello

Is it possible to automatically set an env variable with erlang version number, to solve that notorious deprecaction vs backward compatibility problem? Rebar3 "knows" major release number (since it supports "require_otp_vsn" clause), is there a way to set it in the environment?

BG


--
mężczyzna potrzebuje dwóch narzędzi - taśmy klejącej i WD40. co się rusza, a nie powinno skleić taśmą, a co się nie rusza, a powinno - spryskać WD40.

(mafodope, bash.org.pl)
_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions


_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions