[erlang-questions] rebar3 dependencies

[Alin Popa]

On 19 Mar 2016, at 02:03, Eric Meadows-Jönsson <eric.meadows.jonsson@REDACTED> wrote:

>> Yes, what I am talking about is having all the source code dependencies at a known state.
>> hex attempts to do this, but as you mentioned, is unable to be hosted privately and the public
>> hex site may go down at anytime for any length of time.
> 
> You can host Hex privately, there is nothing prohibiting you from hosting your own Hex repo or mirroring Hex.pm. 
> 
Could you please give us more details on how to do this, or even some unofficial/yet to be released documentation?

Thanks,
Alin

>> On Sat, Mar 19, 2016 at 2:37 AM, Michael Truog <mjtruog@REDACTED> wrote:
>>> On 03/18/2016 05:58 PM, Tristan Sloughter wrote:
>>> You appear to be avoiding the topic of putting all the source code dependencies into a single repository and having them work with rebar3.
>>>  
>>> I think it is unnecessary and poor form. Especially if you application is public and others want to depend on it.
>> 
>> While your opinion is that the approach is "bad", I see it as required for
>> stable and repeatable builds.  So we reach an impasse where it appears that
>> rebar3 is not meant to support this, unless by chance without it
>> intentionally being a use-case, which is unfortunate.
>> 
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
> 
> 
> 
> -- 
> Eric Meadows-Jönsson
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160319/0971f4d8/attachment.htm>