[erlang-questions] rebar3 dependencies

Tristan Sloughter t@REDACTED
Sat Mar 19 15:55:49 CET 2016


Yea, I'd change it to hook before install_deps. No need to do it for
each individual dependency, just copy them all from the vendor dir to
the build dir once before rebar3 tries to resolve dependencies.

-- 
  Tristan Sloughter
  t@REDACTED

On Sat, Mar 19, 2016, at 07:32 AM, Fred Hebert wrote:
> On 03/19, Benoit Chesneau wrote:
> >
> >What do you think about it? Can we right now hooks the way the 
> >dependency is retrieved? Or do we need to provide some kind of custom 
> >dep resource [1] that would proxy each deps?
> 
> http://www.rebar3.org/docs/configuration#section-hookable-points-in-providers
> 
> Currently those are the only hookable providers. Either we'd need to add 
> hookable providers [1], or you could use aliases:
> 
> http://www.rebar3.org/docs/using-available-plugins#alias
> 
> Or run your build as hooks of your vendoring provider.
> 
> >Seem like right now that _checkouts is an hack
> >and something like it can't be done externally.
> 
> It is. The plugin is a better solution.
> 
> [1] probably 
> https://github.com/erlang/rebar3/blob/master/src/rebar_app_discover.erl
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions



More information about the erlang-questions mailing list