Curated HEX packages

[ericmj]

@OvermindDL1

Could go the npm way where a package is either “<packagename>” for a ‘global’ named one, or a specific one that is “<username>/<packagename>”, that allows people to fork all they want and still be accessible.

Hex.pm is adding support for multiple repositories but they will not be public except for the “global” one. But I think the issue is here is exactly the opposite, the people that want a curated package manager doesn’t want forks or alternatives to packages.

@OvermindDL1

True, though that would have been an interesting design decision, put some ‘reponame’ or so as a top level module, would have helped to prevent conflicts, but eh… ^.^

Module names are not enough to namespace against conflicts. You have to also change application names, process names, ets table names and a lot of other things. The VM wasn’t built to support multiple variants of the same application loaded at the same time.