Commit graph

8 commits

Author SHA1 Message Date
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
Maximilian Bosch ba934e9fc1 beam/fetchMixDeps: allow adding patches
Needed to modify e.g. a few things in the `plausible` package to get it
running properly.
2021-06-02 19:21:31 +09:00
happysalada 481832b32d beam-modules: buildMix -> mixRelease 2021-04-08 20:54:48 +09:00
happysalada f38079ff95 use lib only where required
use standard phases
2021-02-01 09:58:51 +09:00
happysalada 39c85b0bcf use correct commands to set local rebar and rebar3 2021-02-01 09:34:44 +09:00
happysalada 10d464e887 remove exporting of .hex 2021-02-01 09:34:44 +09:00
happysalada 28b8e38666 add git dependency 2021-02-01 09:34:44 +09:00
happysalada 7fbb9e8d04 beam-modules: add fetch-mix-deps 2021-02-01 09:34:44 +09:00