Rebar3 support and code sharing

Fair enough, let's leave it as-is then.

On Sat, Oct 11, 2014 at 11:30 AM, Tristan Sloughter <
notifications@github.com> wrote:

> In src/rlx_prv_archive.erl:
>
> >  -spec init(rlx_state:t()) -> {ok, rlx_state:t()}.
> >  init(State) ->
> > -    {ok, State}.
> > +    State1 = rlx_state:add_provider(State, providers:create([{name, ?PROVIDER},
>
> Technically, yes, we could add like a function
> rlx_utils:create_and_add_provider that takes State and the list of
> tuples. But I think this is clearer as is and makes clear you can do
> anything you want here, not simply create and add a provider.
>
> Though I have considered the ability to have init/1 return {ok, State,
> Provider} and having providers module add it to State but that isn't as
> simple since it requires creating a uniformed API for any project that uses
> providers. I may do that with a behaviour eventually.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/erlware/relx/pull/227/files#r18742484>.
>