Deps using old version of rebar
steve at srstrong.com
Mon Mar 12 17:05:18 EDT 2012
Quick question - what's the recommended approach when a dependency is using an old version of rebar, and has a rebar.config that is no longer accepted by the rebar executable used in the root?
Options I've thought of:
* just edit the rebar.config in the dependency. This is quick and dirty, but obviously doesn't work in the long term
* the above, but on a fork. Currently the best option I can think of, but (assuming the owner doesn't accept a pull), not ideal. Obviously, if the owner does take a pull request, then job done :)
* have rebar execute the dependency's rebar executable when recursing instead of trying to process the dependency's rebar.config directly. I'm guessing there would be significant implications with inherited properties here…
* have some way in the root rebar.config of providing an alternate rebar.config for the dependency
-- Steve Strong
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rebar