This repository was archived by the owner on Jul 15, 2020. It is now read-only.
Open
Conversation
Member
|
IIRC @oubiwann wants to make Hex adoption optional. I have a workaround somewhere that uses an env var like |
Author
|
I see. Hex is becoming an standard in the Erlang ecosystem so it's easier for us to have github/gitlab as the optional choice and get the users fetch from Hex instead. I've never used gitlab but I rely on Hex for my Erlang/Elixir projects (and LFE ones aswell). I'm ok if this is not a desired approach. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This enables us to use the rebar3 hex cache instead of cloning the LFE repo all the time.