[erlang-questions] rebar3 dependencies

Tristan Sloughter <>
Sat Mar 19 04:35:13 CET 2016


Yea, don't use _checkouts, that should be for local development and
removes the checkout app from the lock file.

People can try this https://github.com/tsloughter/rebar3_vendor

It has issues if you have git deps... but I think it is a start for
those who need this. Hopefully those who need it can improve it from
here :)

-- 
  Tristan Sloughter
  

On Fri, Mar 18, 2016, at 10:14 PM, Fred Hebert wrote:
> On 03/18, Geoff Cant wrote:
> >Wouldn't checkouts work for this case?
> >
> 
> Yes and no. _checkouts work fine for local development, but it still 
> carries that pesky ebin/.
> 
> Tristan and I are discussing plugins for this. You could really have 
> `rebar3 vendor store' which copies from `_build/<profile>/lib' to 
> `deps/'  (minus the ebins), and `rebar3 vendor apply' which moves them 
> back to `_build/<profile>/lib'.
> 
> The plugin would only need to copy/move files around, and could still 
> use the rest of all rebar3's providers, without having us maintain it in 
> core.
> 
> That way you can experiment with upgrades, blowing stuff up, crushing 
> it, and so on, and still vendor your stuff in.
> 
> There's simple solutions for it, and we're hoping people can use the 
> plugin interface for that.


More information about the erlang-questions mailing list