<div>
<br>
</div>
<div></div>
<p style="color: #A0A0A8;">On Friday, April 13, 2012 at 12:14 PM, Alvaro Videla wrote:</p><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<p style="color: #A0A0A8;">On Friday, April 13, 2012 at 5:59 PM, Matthew Sackman wrote:</p></div></div></span> What happens if each of those packages ships a<span><div><div><blockquote type="cite"><div>
<span><div><div><div>different version of Erlang? Do you try and get the different nodes to</div><div>talk to each other etc etc?</div></div></div></span></div></blockquote><div>I think the idea of such package is mostly to ease adoption. If you want to make internode communication between Riak, Ejabberd and RabbitMQ then you probably know how to get your Erlang up and running.</div></div></div></span></blockquote><div>+1 </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div><br></div><div>BTW, creating this .tar is something supported by OTP, it's not a hack. So I guess someone is using that in production already. The guys behind erlware created this tool to work with releases: <a href="https://github.com/erlware/sinan/wiki">https://github.com/erlware/sinan/wiki</a> so I guess they probably use that. Also rebar supports generating releases, I guess that's what Riak does with their distros.</div></div></div></span></blockquote><div>+1 </div><div><br></div><div>Cheers,</div><div><br></div><div>Gavin</div>