rebar is not ready for production
Par Mathieu Lecarme le mercredi, 21 juillet 2010, 12:29 - Lien permanent
Rebar is the apple in heaven. Erlang bites it. First rebar was made as a compilation tools. You just do ./rebar compile, and it compiles new things, erlang files, C files, wathever can be compiled. Then, erlang saw that each project wasn't alone in the galaxy. So dependency appears. ./rebar get-deps. Heavean is now lost. Dependency can handle differents VSC tools. Basho stuff use mercurial, other stuff use git. But I don't wont to depend on master branch, I wont release, I wont determinist dependences. Releases means http download, I don't wont to install mercurial+subversion+git for compiling erlang product.
Dependencies uses regex pattern for version matching. I never see it working well, if you don't wont to kill some swedish kitten, just use .* pattern, relax yourself, and pray.
I don't wont to fork every erlang's github project to be able to use it. I just wont simple tools like ruby gem or erlang pip.
I wont to use erlang in production, not only as proof of concept.