You can also list all the dependencies explicitly, with tags or refs, in
top-level rebar.config. Of course, if dependencies list changes for
whatever reason (it happened to Riak's Erlang client once), you'll still be
in trouble.
On Tue, Apr 9, 2013 at 10:48 AM, Daniil Churikov wrote:
> Hello Yu
Hello Yuri.
A while ago we faced same problem. Our solution was to fork all repositories
we depends on to our public account, fix all rebar.config of all deps to
point on our repos and update any repos manually. Also when we need to lock
deps, as you mentioned, we use rebar lock plugin and recursi
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 bi
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
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 proj
