<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 25 Sep 2017, at 22.32, Tristan Sloughter <<a href="mailto:t@crashfast.com" class="">t@crashfast.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: SourceCodeProForPowerline-Regular; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">may be solved simply with existing tools like makeself</span></div></blockquote></div><br class=""><div class="">+1. </div><div class=""><br class=""></div><div class="">There are not issue to package Erlang release to tarball and then to self-extractable archive. This is what I am doing on daily basic. I am trying to understand why community rejects this approach and targets some complex tooling? Is this because of Windows platform support or escripts? Or something else?</div><div class=""><br class=""></div><div class="">- Dmitry</div></body></html>