A story about unexpected changes in riak-erlang-client dependencies

Dmitry Demeshchuk demeshchuk at gmail.com
Tue Apr 9 13:54:54 EDT 2013

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 <ddosia at gmail.com> wrote:

> 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 recursively lock all
> deps on same commit.
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/A-story-about-unexpected-changes-in-riak-erlang-client-dependencies-tp4027582p4027594.html
> Sent from the Riak Users mailing list archive at Nabble.com.
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Best regards,
Dmitry Demeshchuk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20130409/e4d4adc6/attachment.html>

More information about the riak-users mailing list