Hi Frerich Raabe,
Thank you for the detailed proposal.
Unfortunately, the issue with ~> 0.1 is that people may expect us to
perform proper dependency resolution. The dependency resolution does not
consider only how to download the package "foo" but rather the package
"foo" and all of its
I believe that this already works, as I have one dependency in a
project where I am not able to do this because the maintainer
explicitly leaves the git version as `0.0.0` and applies the correct
version during their release process.
https://github.com/rzane/file_store/issues/24
-a
On Sat, Oct
Hi all,
specifying dependencies in `mix.exs` files via Git repositories could be
made
more powerful (and arguably reduce the need for self-hosted Hex
repositories)
by adding support for version requirements. To support this, Mix could
automatically map Git tags to versions which can be consumed
