[erlang-questions] Reltool anyone?

Tristan Sloughter tristan.sloughter@REDACTED
Sun Aug 17 18:24:38 CEST 2014

Yes, rebar does nothing to help with reltool. And I'd argue it almost makes
it worse. Loic points to https://github.com/erlware/relx not to rebar.

Though hopefully rebar will use relx instead of reltool soon enough.

On Sun, Aug 17, 2014 at 11:23 AM, Ulf Wiger <ulf@REDACTED> wrote:

> On 17 Aug 2014, at 18:15, Loïc Hoguin <essen@REDACTED> wrote:
> > Teaching reltool today seems quite counter productive, it is the kind of
> knowledge that you want tool implementors to have, but not normal users.
> True, but even when using reltool via rebar, you end up having to
> understand quite a lot about reltool. The only things rebar actually helps
> with are (1) generating a template for you to modify, and (2) actually
> starting reltool. But extending the reltool.config and understanding why it
> bombs tend to throw you deep into the mysteries of reltool, and rebar does
> practically nothing to buffer this.
> If something needs to be documented in this area, it would be
> Troubleshooting Reltool, IMHO: what are the typical errors, and how do they
> manifest themselves?
> BR,
> Ulf W
> (I was quite instrumental in advising Dizzy to use reltool in rebar at the
> time, so for those of you who are unhappy about that choice, feel free to
> blame me. The thinking was that rebar should rely on core OTP functionality
> rather than compete with it.)
> Ulf Wiger, Co-founder & Developer Advocate, Feuerlabs Inc.
> http://feuerlabs.com
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140817/bec91eda/attachment.htm>

More information about the erlang-questions mailing list