[erlang-questions] Erlang package manager
Fri Jan 2 20:34:42 CET 2015
Is there really a need to try to compete with OS-specific or OS-agnostic PM's?
For Erlang PM (which is being discussed here), why not limit the scope
to erlang-only packages & deps?
E.g., Java PM's (Ivy, Maven, Ant) focus on Java code, don't they?
One of the key benefits of building / designating an "official" Erlang
PM would be ease of use of | conversion from a variety of existing
Erlang-specific PM's/build tools.
In other words, "the Erlang PM" would install 90% of Erlang packages
in the wild, or ideally from a central repository.
More information about the erlang-questions