<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On 19 Mar 2016, at 02:03, Eric Meadows-Jönsson <<a href="mailto:eric.meadows.jonsson@gmail.com">eric.meadows.jonsson@gmail.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">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.</blockquote><div><br></div><div>You can host Hex privately, there is nothing prohibiting you from hosting your own Hex repo or mirroring Hex.pm. </div></div><div class="gmail_extra"><br></div></div></blockquote>Could you please give us more details on how to do this, or even some unofficial/yet to be released documentation?<div><br></div><div>Thanks,</div><div>Alin<br><div><br><blockquote type="cite"><div><div class="gmail_extra"><div class="gmail_quote">On Sat, Mar 19, 2016 at 2:37 AM, Michael Truog <span dir="ltr"><<a href="mailto:mjtruog@gmail.com" target="_blank">mjtruog@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div>On 03/18/2016 05:58 PM, Tristan
Sloughter wrote:<br>
</div>
<blockquote type="cite">
<blockquote>
<div>You appear to be avoiding the topic of putting all the
source code dependencies into a single repository and having
them work with rebar3.<br>
</div>
</blockquote>
<div> </div>
<div>I think it is unnecessary and poor form. Especially if you
application is public and others want to depend on it.<br>
</div>
</blockquote>
<br>
</span><tt>While your opinion is that the approach is "bad", I see it as
required for<br>
stable and repeatable builds. So we reach an impasse where it
appears that<br>
rebar3 is not meant to support this, unless by chance without it<br>
intentionally being a use-case, which is unfortunate.<br>
</tt>
</div>
<br>_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Eric Meadows-Jönsson</div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>erlang-questions mailing list</span><br><span><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a></span><br><span><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></span><br></div></blockquote></div></div></body></html>