2a9336b426
The Elixir LS package in Nixpkgs by default used the latest Elixir version available to compile and run Elixir LS. The user can build a custom Elixir LS package with a different Elixir version: my-custom-elixir-ls = pkgs.elixir-ls.override { elixir = my-custom-elixir; }; But by doing so the user changes only the Elixir version used to run Elixir LS; the Elixir version used to compile Elixir LS doesn't change. As the result, the custom Elixir LS package uses a different Elixir version at runtime than the Elixir version it was compiled with. In order to be able to modify the Elixir version used at build time, I changed `mixRelease` and `fetchMixDeps` to accept `elixir` and `hex` as parameters (defaults to the latest Elixir and Hex packages). |
||
---|---|---|
.. | ||
elixir-ls | ||
elvis-erlang | ||
erlang-ls | ||
erlfmt | ||
hex | ||
pc | ||
pgsql | ||
rebar3-nix | ||
rebar3-proper | ||
webdriver | ||
build-erlang-mk.nix | ||
build-hex.nix | ||
build-mix.nix | ||
build-rebar3.nix | ||
default.nix | ||
fetch-hex.nix | ||
fetch-mix-deps.nix | ||
fetch-rebar-deps.nix | ||
lib.nix | ||
mix-configure-hook.sh | ||
mix-release.nix | ||
rebar3-release.nix |