[erlang-questions] rebar3 dependencies
Sat Mar 19 22:06:31 CET 2016
I'm pretty sure we always said it was possible with plugins or custom
resources when it was brought up. Which remains the case.
On Sat, Mar 19, 2016, at 01:36 PM, Michael Truog wrote:
> On 03/19/2016 05:24 AM, Fred Hebert wrote:
> > On 03/19, Roberto Ostinelli wrote:
> >> Tristan, Fred, Eric
> >> That being said, I'd like for you, Tristan, Fred, Eric, to try and welcome
> >> my little feedback here, and take it for what it is. I'd like it to be easy
> >> and possible to discuss these ideas serenely, because relying on a system
> >> that considers (or better yet, values) the community input such as mine
> >> would make me sleep better at night :)
> > We do, Tristan even started a toy plugin here for you :)
> > It would certainly have been easier for us if these concerns had been brought to us in the last year and a half we have spent in beta, alpha and pre-alpha, though, rather than week 1 after stable release.
> > It's now too late to change the core, so we must think in plugins. Hopefully what we can come up with will prove satisfactory.
> > _______________________________________________
> > erlang-questions mailing list
> > http://erlang.org/mailman/listinfo/erlang-questions
> > .
> I have made sure to ask about this in the past, so I don't think you can
> ignorance on this use-case. The vendor plugin has been the first attempt
> at a clear response, for which I am grateful. rebar2 had its core
> to become rebar3 and any source code that is not dead can change.
> So, I see no reason why rebar3 is unable to change. It isn't as if
> has a technical design document to follow in a waterfall model or fits to
> an ISO spec, or even an RFC.
> erlang-questions mailing list
More information about the erlang-questions