[erlang-questions] Erlang package manager

Dmytro Lytovchenko <>
Sun Dec 28 13:02:33 CET 2014


Its not up to ESL to decide what gets chosen, OTP/E/// and IUG will decide
the final options and budget according to what is discussed here. But ESL
may offer a person to work on this budget and this project.

>From my personal point of view,
- Nix has a chance because its C++ which is potentially cross platform and
compiles everywhere. Also from NIH point of view - huge work was done there
and it would be silly to just throw the idea away because parts of it are
not compatible - this can be fixed;
- pure C or C++ implementation from scratch has a chance because its cross
platform and compiles everywhere (or it should by design);
- pure Erlang implementation although doesn't exist yet only in a form of
non-working bare skeleton prototype, also has a chance
- and then Elixir implementation has slim chance because carrying Elixir
compiler or compiled BEAM's in OTP source may be non-desirable.

On Sat, Dec 27, 2014 at 4:33 PM, Tristan Sloughter <> wrote:

> Erlang Solutions certainly won't be going the nix route.
>
> So someone should just go try it already :P. I did and gave up and
> tossed it in the garbage.
>
> I say this because I feel the conversation is pointless and has
> completely derailed any talk of an actual solution to real problems.
>
> --
>   Tristan Sloughter
>   
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141228/9ff999b9/attachment.html>


More information about the erlang-questions mailing list