<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 03/18/2016 05:32 PM, Tristan
Sloughter wrote:<br>
</div>
<blockquote
cite="mid:1458347567.2174564.553539442.66BE7E14@webmail.messagingengine.com"
type="cite">
<title></title>
<blockquote>
<div dir="ltr">This use-case of rebar is an important one due to
Erlang's focus on fault-tolerance. To make sure your built is
robust and stable,
it requires having all your dependencies at a known state.<br>
</div>
</blockquote>
<div> </div>
<div>Your build artifact for deployment is a release which does
"bundle" all dependencies at a certain point in time.<br>
</div>
<div> </div>
<div>For reproducibility in the event of losing the original
release is, as you mention, what the lock files are for. When
hex gains easy mirroring there will also be a quick way to
ensure you have your own backups of alls your dependencies.<br>
</div>
</blockquote>
<tt>Yes, what I am talking about is having all the source code
dependencies at a known state.<br>
hex attempts to do this, but as you mentioned, is unable to be
hosted privately and the public<br>
hex site may go down at anytime for any length of time.<br>
<br>
You appear to be avoiding the topic of putting all the source code
dependencies into a<br>
single repository and having them work with rebar3.<br>
</tt>
</body>
</html>