Use kerl for managing Erlang versions #54
This PR is inspired by:
And aims to address issue #53.
Benefits over the existing asdf-erlang code:
Benefits over asdf-kerl:
Noticed one rough edge with this implementation. The asdf-erlang's version of kerl interferes with user's installed version of kerl. For example the user can view asdf-erlang builds with their own installation of kerl in certain scenarios. This can be solved by setting
I also need to go back through and remove some code. I was thinking kerl didn't install docs, but it looks like it does so I can remove my custom docs code from the plugin.
The `ref:OTP-20.1.2` syntax described in i.e. asdf-vm#42 and asdf-vm#48 no longer work after the transition to use `kerl` under the hood, when asdf-vm#54 got merged. This environment variable instructs `kerl` to parse Git tags rather than the original source (erlang.org?). If the maintainers would prefer, I can instead submit a documentation update, as this configuration can also be placed in `~/.kerlrc`. kerl/kerl#240
Sorry for being late for the party, I'm now back from Christmas holidays.
@Stratus3D Very nice work, I really like the integration! I think setting
I guess the