Agner: A Giant Nebula of Erlang Repositories

For example, in order to use entop command line utility, you had to clone two repos, build both of them and use that script from the directory where you built entop. And lots of erlang packages are like that.

With agner, you just do $ agner install entop and you're done, it's in your PATH

1. central index/indices

2. granular overlaying (you can overlay specific packages and don't have to maintain your fork of a global repo)

3. granular permissions, allowing maintainers to work on their packages without going through the hassle of pull requests and associated bottleneck problems (the "homebrew problem")

4. usage of tags and branches for versioning primitives

5. independence from original repository

6. ability to use multiple repositories

7. (in the future) ability to use non-SCM fetching methods (aka "tarball")

That's for starters. Good enough? :)

It would absolutely benefit Erlang to heal over this gap -- not that having separate tools is a bad thing at all, but the fact that both ecosystems often seem so blissfully unaware of the other :)