In regards to 3rd parties, we've generally had good luck asking the developer to make a tag for us or to merge a branch that has fixed dependencies. I do agree it is a problem, but it is one that can be fixed.
Sorry you ran into problems in any of our repos, we are working to fix our process a bit so folks using our code don't hit the problems you hit. -Jared On Tue, Apr 9, 2013 at 9:44 AM, Yuri Lukyanov <[email protected]> wrote: > Glad to hear you are moving away from master dependencies. Would be > great if all of us follow this way. It's sad that even if you > completely sorted out your own deps and rebar.conig's, it does not > solve the problem in general. You may still want to use third-party > deps which are not necessary good in terms of dependency management > policy. And you end up forking those projects for one reason only: to > fix their rebar.config's and create tags. Not mentioning the headache > when you want to update your forked versions with newer versions from > original repositories... > > Looks like we are far away from the perfect dependency world :) > > On Tue, Apr 9, 2013 at 7:15 PM, Reid Draper <[email protected]> wrote: > > Yuri, > > > > You're certainly not the only one dealing with this. Sorry about that. > It's bit us here at Basho a few times too. As you saw, we're moving toward > not having master dependencies, at least for tagged versions of repos. > Especially for projects that are likely to be dependencies in other > projects (ie. our client libraries, lager, etc.). That being said, it will > take us some time to get there. You should also be aware of another 'fun' > issue with rebar: if multiple dependencies require the same dep, the > version that rebar first encounters will be the one that gets used. You'll > find it helpful to use `./rebar list-deps` to see exactly what's being used > in your project. I agree that this is something the Erlang community could > improve, but in the short-term we're going to be more diligent about using > recursively using tags for all tagged repos. > > > > Reid > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
