Another (probably better) approach is the one done by @hauleth - I haven’t explored in detail yet.
→ github.com/hauleth/nix-elixir
Mentioned over here:
- What's the current best-in-class approach to packaging Elixir/Erlang/BEAM applications using Nix+releases as of July 2020? - #6 by anon31783435
- github.com/NixOS/nixpkgs/pull/97245
On my side, with the compilation time improvements within Elixir v1.11,
I will start to get even more “un-pure” and try to reuse _build & deps.
Build time within CI is a major important thing for me.
But I’ve already mentioned I use Nix as a sharable development environment setup
and for perfect fast cache-able CI.
So my preferences may differ.
Other things about the state of the BEAM within Nix:
I’ve prepared the update of Erlang to v23.1 → github.com/NixOS/nixpkgs/pull/98646.
But it’s once again slow in getting adopted.
For me to have a perfect development environment it’s important to have latest versions fast available…
I also would prefer if we don’t prolong the update of the default Erlang within Nix too long.
So in my opinion it should be time now to change from v22 to v23.1.
I’ve a look into upgrading rebar3 to the latest version, as the current one would probably not build with Erlang v23.
But the rebar3 pkg seems too complicated for my Nix skills…
Good for now - all the best.