[erlang-questions] Erlang package manager

[Benoit Chesneau]

On Wed, Dec 17, 2014 at 1:18 AM, Tristan Sloughter <t@REDACTED> wrote:
>
> I'm just throwing my thoughts out there. This isn't to cover all
> features I'd want to see in a package manager, but instead just the ones
> I know are "controversial". These are also the direction we've gone with
> rebar3 (http://rebar3.org).
>
> * Binary packages
>
> Why build from source if you don't need to? Most Erlang applications
> have no native code.
>
> * No semver enforcement
>
> I mean, why bother? For one, you can't actually force semantic
> versioning. You can require the version be of the format
> MAJOR.MINOR.PATCH+[metadata] but not the semantic part.
>
> I think forcing the format in the name of "semver" is confusing and
> wrong.
>
> * Strict version declarations
>
> No ">=1.0" or "<1.0 and >0.5". The project should set a version number
> of the dependency it relies on.
>
> "Solving" dependencies is a matter of choosing the highest version of a
> dep in the dependency tree. This is also followed by maven,
>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html



What if you want to support a package from version 3 to 5 but not 6 neither
1 or 2 due  breaking changes in the API?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141217/742a25bc/attachment.htm>