<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>We are explaining how OTP works by explaining what is going on behind the scenes. A different approach I found out worked better when teaching behaviours than diving straight into callback hell. Release handling, on the other hand, has always been the black sheep because of the lack of a unified approach. Everyone has historically reached (potentially different) goals in different ways, often depending on what they were used to and comfortable with from previous (non Erlang) jobs. </div><div><br></div><div>Buy me or Ulf a beer and we will tell you how release handling was done with the Axd301. You must have a strong stomach, as it is not for the faint of heart :-)</div><div><br></div><div>F<br><br><div><br></div></div><div><br>On 17 Aug 2014, at 18:58, Tristan Sloughter <<a href="mailto:tristan.sloughter@gmail.com">tristan.sloughter@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>I find it confusing when books spend so much time on what should be considered more of an internals matter, like manually building a release, which is found in an appendix or online docs<br><br>It isn't something you'd do in real life, but yes it is something you would benefit from knowing once you are dealing with building and deploying releases even when using a higher level tool like reltool or relx.<br>
<br></div>Just my 2 cents :)<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Aug 17, 2014 at 11:39 AM, Francesco Cesarini <span dir="ltr"><<a href="mailto:francesco@erlang-solutions.com" target="_blank">francesco@erlang-solutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
We are covering relx and rebar and might add more tools based on
feedback we receive from the reviewers. <br>
<br>
Also for those wondering - So far, we have about 30 pages on release
handling. In line with the rest of the book, we are explaining in
detail what is happening behind the scenes and how to manually
create a release. From there, we show you how to automate it and use
the tools. <br><span class="HOEnZb"><font color="#888888">
<br>
/F</font></span><div><div class="h5"><br>
<br>
<div>On 17/08/2014 17:23, Tristan Sloughter
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>I'm pretty sure "counter intuitive" and "will make your
struggle" are reltool's best known features.<br>
<br>
</div>
Which is why relx (<a href="https://github.com/erlware/relx" target="_blank">https://github.com/erlware/relx</a>)
has been catching on :)<br>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Aug 17, 2014 at 11:07 AM,
Francesco Cesarini <span dir="ltr"><<a href="mailto:francesco@erlang-solutions.com" target="_blank">francesco@erlang-solutions.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I was wrapping up the chapter on release handling for
the OTP book and never having used it before, decided
to take a look at reltool. Is anyone using it? I am
finding it counter intuitive and struggling to see how
it simplifies the task of creating releases.<br>
<br>
Feel free to reply to the list or ping me privately.<br>
<br>
Thanks,<br>
F<span><font color="#888888"><br>
<br>
-- <br>
Founder & Technical Director<br>
Erlang Solutions Ltd.<br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<pre cols="72">--
Founder & Technical Director
Erlang Solutions Ltd.
</pre>
</div></div></div>
</blockquote></div><br></div>
</div></blockquote></body></html>