> Hey, I was the one who implemented that feature in Bundler. :) >
Hah, that's cool. I swear you've written half the software I really like using. :) > One other possible way of supporting this is by using environment > variables and handling the logic in your mix.exs. > My only complaint with bundler's way is rooted in its non-explicit and spread-out configuration system. It takes foreknowledge and several commands to set up local repos or figure out what's going on, so I like the idea of something more explicit and centralized than ENV vars. In particular, path dependencies were written so they never change the > lock, so it already provides part of the functionality I had to implement > for the local git repo thing. That's great, I didn't know that! This is really the only reason why this would have *needed* to be a Mix feature request instead of a useful mix.exs pattern. I'll play around with in-mix-file options and see if/how they work best, and report back if there's something worth adding to mix. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/88ad8710-50d3-44ba-ab92-a022204b4e37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
