[erlang-questions] Erlang package manager

Mark Nijhof <>
Fri Jan 2 21:54:24 CET 2015


Hehe I knew there would be some protest when I mentioned NPM, but look at
their success, probably a big reason for the adaption of Node, it makes
getting started easy. Erlang.mk does a lot towards this as well already,
discovery is an issue though.

On Fri, Jan 2, 2015 at 9:10 PM, nx <> wrote:

> 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 <> 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.
> >
> > Tristan
> >
> > _______________________________________________
> > erlang-questions mailing list
> > 
> > http://erlang.org/mailman/listinfo/erlang-questions
> >
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>



-- 
Mark Nijhof
t:   @MarkNijhof <https://twitter.com/MarkNijhof>
s:  marknijhof
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150102/3ffa0c2b/attachment.html>


More information about the erlang-questions mailing list