Louis Pilfold <[email protected]> schrieb am Di., 18. Juli 2017 um 23:37 Uhr:
> Hey Vitaly
>
> The dependency file for mix is an Elixir program rather than just a simple
> JSON file. There's no way reliably and safely programatically modify the
> mix.exs file as a result.
>
This is a thing I do totally understand, and I won't argue about.
But what if did the following workflow?
$ mix deps.preload ecto
[...] downloading most recent version of ecto and its dependencies that
fits into current set of constraints [...]
Please add `{:ecto, "~> 2.1"}' to your deps.
$ edit mix.exs
# edit deps
$ mix deps.compile
This way, we do get the most current version of ecto that is capable to
work with our project and we do get a hint on what we have to add to our
mix-file.
Even though we have to add that line manually, the burden to manually check
versions has been taken from the developer.
Of course, there is much room to discuss how to actually name that task.
Perhaps even have it in `hex`?
Cheers,
> Louis
>
Bye,
Norbert
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elixir-lang-core/CA%2BbCVsuEhuZ9rOC3u9d7928giQr%2BjrW58yiSwUGR2ci3SdJ%2B6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
