summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorSergei Maximov <s.b.maximov@gmail.com>2021-11-02 15:57:13 +0300
committerRaphael Megzari <raphael@megzari.com>2021-11-03 08:46:46 +0900
commit2a9336b426753b1f948bed19c97f07b0f081be46 (patch)
tree3492627a952697e51ae640133046f13fdade5ff6 /pkgs/development/python-modules/rangehttpserver
parent45891c5f1c9d03397e8a77a35214a4ce83dc597d (diff)
elixir-ls: build LS using the same Elixir version that is used to run LS
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).
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions