<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 07:03 PM, Eric
Meadows-Jönsson wrote:<br>
</div>
<blockquote
cite="mid:CAM_eapgW_j35u2y83N8_m2bKqcN=H8BMc8LGSCcVGPP0=t_SHg@mail.gmail.com"
type="cite">
<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. <br>
</div>
</div>
</blockquote>
<br>
While this may be possible, it is undocumented functionality, so it
doesn't exist in a useable way.<br>
The same was true of sinan/faxien in the past.<br>
<br>
<blockquote
cite="mid:CAM_eapgW_j35u2y83N8_m2bKqcN=H8BMc8LGSCcVGPP0=t_SHg@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Mar 19, 2016 at 2:37 AM,
Michael Truog <span dir="ltr"><<a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true"
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>