It wouldn’t be a problem for rebar3 users because rebar3 does not consider version conflicts when resolving dependencies.
ericmj
Elixir Core Team
tristan
Rebar3 Core Team
filmor
What I would like to have is to seamlessly depend on an Elixir package (or just Elixir itself) for usage in a pure-Erlang package, which requires being able to pull Elixir itself in as a dependency. It’s just a set of OTP applications anyway, but I need its functionality at both run- and compile-time.
This would help a lot in unifying the ecosystems because then I’d have a real chance of using all the fancy things that are being built on the Elixir-side of the fence without switching to mix (which is to me currently the only viable option of using Elixir deps). I tried for a while in ierl to get Elixir working in there through rebar3, but in the end gave up and just used mix s.t. the escriptized build included all dependencies correctly.
0
ericmj
Elixir Core Team
ericmj
Elixir Core Team
It becomes a problem for Elixir developers when packages that depend on the Elixir Hex package is published.
0
josevalim
Creator of Elixir
That’s inaccurate in so many levels. 
As Eric pointed out, Mix was designed by Raynes, a Clojure developer, and inspired on leiningen. For years we kept checking with Raynes to make sure the tool was evolving as he planned.
Plus we don’t duplicate Ruby things because they are Ruby things. We “duplicate” Ruby things when we believe they are the best ones to duplicate after comparing many options.
Eh, I did try to contribute to Rebar at the time, but all proposals, including Elixir support, were politely declined. So we were tolerating Makefiles for a while until Raynes stepped up with Mix.
It is happening. Docs, Hex, :telemetry is being rewritten to Erlang to improve compatibility, etc. Releases share common functionality (and bound to share more as we integrate them into Elixir), The new OTP logger is easier to integrate with, etc. But unfortunately we won’t be able to unify everything.
8
tristan
Rebar3 Core Team
Have you tried GitHub - Supersonido/rebar_mix: rebar3 plugin for building Elixir dependencies with mix · GitHub with the latest rebar3 release?
0
filmor
No, not yet. Also, I have to check whether this really helps me, since I’m not actually using a particular Elixir library but the Elixir compiler and auto-completion stuff itself. Since my code is Erlang, I just need to somehow make sure that the respective applications are available at runtime, which (for an escript) I have only been able to achieve reasonably by using Mix directly. If Elixir was a Hex package, it would get embedded just fine.
0
tristan
Rebar3 Core Team
Hah, that is pretty funny since we were checking with leiningen creator technomancy while developing rebar3 – part of why dependencies are resolved the way they are and rebar3 executes all command dependencies of a command each time it is run.
Yea, rebar was just not possible to move forward and had to have a clean break. Both mix and rebar3 were right to do that.
Meant to come here to say the same thing :). Very happy with all the recent joint work on tooling like hex_core and telemetry.
There is plenty to do but I think we are moving in the right direction. And hell, there is still the issue of reltool v relx in OTP 
so there is work still to do just in reducing fragmentation within Erlang itself.
5
tristan
Rebar3 Core Team
Ah, yea, this is only useful if you have some hex dependencies that must be built with Mix.
0