I forgot to say that Erlang packages may need Non Erlang application, like Postgresql, or Varnish or (fill blanks).<br>Debian Meta package allow this, for instance. This could not be achieved with a specific Erlang packager.<br><br><br><br>« Envoyé depuis mon mobile » Eric<br><br>Eric Pailleau <eric.pailleau@wanadoo.fr> a écrit :<br><br>+1<br>Why not generating OS packages instead reinvent the wheel ? Each dependance could be a package itself and Ports source packages.<br>There is also nugets and chocolatey for Windows.<br><br>« Envoyé depuis mon mobile » Eric<br><br>Gleb Peregud <gleber.p@gmail.com> a écrit :<br><br><p dir="ltr">I would really like to see hermiticity and reproducibility of Nix package manager. </p>
<div class="gmail_quote">On Dec 16, 2014 2:09 PM, "Fred Hebert" <<a href="mailto:mononcqc@ferd.ca">mononcqc@ferd.ca</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/16, Bruce Yinhe wrote:<br>
> - What metadata information should an Erlang package include?<br>
> - What functionality do you need in a package manager for Erlang in<br>
> order to use it in production?<br>
> - What other concerns do you have about an Erlang package management<br>
> system?<br>
<br>
I'd certainly like to see signing addressed by a would-be package manager.<br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>