On Tuesday 6 January at 18:00GMT we will be doing a live podcast on a G+ hangout about package management systems. We invite everyone to come join us and submit questions via text chat.
Look at Nix https://nixos.org/nix/ they have some interesting ideas not found on other package managers. Also you should put a lot more thought into this. Erlang acceptance depends on getting this thing right, people will judge the Erlang ecosystem on its package manager. Once itâs released it will be hard (perhaps impossible) to turn around and do it again. That is why it took _years_ for maps to appear in Erlang (because it was done as an afterthought).
Also you should at Canonical. They require you to push your sources with the deb build files and they build the package from source for you. That way they know they can produce the binary without your help.
I have to do with package managers every day, thatâs why I wrote a blog post about them with a comparison matrix: http://blog.versioneye.com/2014/01/15/which-programming-language-has-the-best-package-manager/. I would have to design a new package manager it would be a combination of Composer and the good parts of Maven ;-)
Pingback: 054 Packages | Mostly Erlang
Look at Nix https://nixos.org/nix/ they have some interesting ideas not found on other package managers. Also you should put a lot more thought into this. Erlang acceptance depends on getting this thing right, people will judge the Erlang ecosystem on its package manager. Once itâs released it will be hard (perhaps impossible) to turn around and do it again. That is why it took _years_ for maps to appear in Erlang (because it was done as an afterthought).
Also you should at Canonical. They require you to push your sources with the deb build files and they build the package from source for you. That way they know they can produce the binary without your help.