Commit graph

10 commits

Author SHA1 Message Date
Gaetan Lepage 43c964b1be elixir-ls: fix build 2023-03-23 09:25:46 +01:00
superherointj 1f24ebb428 elixir-ls: rename elixir_ls to elixir-ls 2023-03-20 17:57:35 -04:00
arathunku cec45b0a1c
elixir-ls: 0.12.0 -> 0.13.0 2023-01-19 20:44:11 +01:00
arathunku 23f765df13
elixir-ls: 0.11.0 -> 0.12.0 2022-11-17 21:11:09 +01:00
Erwin Boskma fa325eafe8 elixir-ls: 0.10.0 -> 0.11.0 2022-08-24 22:02:35 -04:00
arathunku e464e032d8 elixir-ls: 0.9.0 -> 0.10.0 2022-07-08 04:23:11 -04:00
Raphael Megzari 89d416b670
elixir-ls: 0.8.1 -> 0.9.0 (#148671) 2021-12-08 09:11:35 +09:00
Sergei Maximov 2a9336b426 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).
2021-11-03 08:46:46 +09:00
happysalada f2b50ffadb elixir-ls: 0.8.0 -> 0.8.1 2021-09-02 23:00:02 +09:00
happysalada 070fa4cefc elixir_ls: add update script 2021-09-02 10:55:45 +09:00