You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how this will account for different OTP versions that Elixir could be compiled with. Do you see something that could help find this? I don't see anything in mix.exs that specifies the OTP version, unless folks just add it. For example:
Let's say that 1.5.2 is the latest Elixir version, and mix.exs specifies elixir: "~> 1.5". At the time asdf install is ran, does it fetch the latest 1.5.x version or earliest? If latest, and then later 1.5.3 releases, should asdf install require 1.5.3? Would asdf say the "specified" version is not yet installed, or would it be satisfied? I figure if folks want a specific version of Elixir for their app, they could specify elixir: "1.5.2" instead. Should there be a .tool-versions.lock generated until explicitly told to upgrade? (I figure this is a bigger question for asdf).
In addition to the
.exenv-version
file, asdf-elixir should also be able to read the Elixir version out of amix.exs
file in the current directory.See this related issue for kiex: taylor/kiex#54
The text was updated successfully, but these errors were encountered: