[erlang-questions] Erlang package manager
Fri Jan 2 21:10:35 CET 2015
Gah! I wanted to call the Erlang packages Crates. And have the package
index be called Logistics. Thought those names went well with Rebar.
Oh well. Guess we'll have to call Erlang packages Lollipops or
something and have the package index be called Candyland. That's the
only viable naming alternative at this point.
On Fri, Jan 2, 2015 at 3:02 PM, Tristan Sloughter <t@REDACTED> wrote:
> The strongest reason I can see to build an Erlang centric PM is to support
> Erlang's existing deployment behaviors i.e. releases.
> An Erlang centric PM should not do anything regarding releases.
> The PM should focus on development and not for deployment. Releases should
> be used to build target systems and deployed as such, maybe the libs that
> are used to build the release/target system were fetched with the PM at some
> point but the PM needs no knowledge of releases.
> As for npm, gems, bundler, maven I know little about any of them. Except
> that one is worth millions of dollars or something... And relies on CouchDB
> and has hilarious outcomes when someone breaks semver rules. Anyway... I
> don't think there is anything people are proposing we take directly from
> those, instead to learn from prior art -- I'd suggest more opam/cabal/cpan
> than those as useful prior art though.
> Cargo, http://crates.io, is an example of the condensed knowledge taken from
> those projects into a new package manager.
> But I do like Maven's(and thus Leiningens) dependency handling, highest spot
> on the dep tree wins. And we are using that for rebar3.
> erlang-questions mailing list
More information about the erlang-questions