Agner is an erlang package manager - related to rubygems or python's easyinstall. It's distributed as a curl > sh oneliner right now that makes it look reasonably easy ebuild.
I'd volunteer to put together an original ebuild if there's interest.
Please fill in the URL field using the package's home page.
Can anyone think of a good category? Perhaps app-portage/agner?
(In reply to comment #2)
> Can anyone think of a good category? Perhaps app-portage/agner?
I could be a nice to create dev-erlang category (like setuptools is in dev-python)
(In reply to Judson from comment #0)
> Agner is an erlang package manager - related to rubygems or python's
> easyinstall. It's distributed as a curl > sh oneliner right now that makes
> it look reasonably easy ebuild.
This raises some red flags. It is my experience that projects which distribute themselves in this fashion tend to not be very security conscious. Please see bug 537162, though admittedly Haskell has more traditional distribution methods. This was only recently fixed (and I am currently finding documentation to cite for that bug, so I can close it).
If at all possible I would like to prevent insecure packages (or package managers) from being added so that the situation with cabal-install does not repeat itself.
I tried to audit agner myself, but the website (http://erlagner.org/) does not contain the aforementioned curl > sh line or really any information at all. Has the project been abandoned? When I searched for it I had a hard time turning up results, though that was because I used the shorter form of the project's name which is a popular given name of historical significance.
(In reply to Paul Labedan from comment #3)
> (In reply to comment #2)
> > Can anyone think of a good category? Perhaps app-portage/agner?
> I could be a nice to create dev-erlang category (like setuptools is in
If there are enough packages I agree this would be a good idea. I would hope the situation with dev-haskell packages (they tend to have extremely general names that may be duplicates of other packages) is avoided, but it might not be possible.
As a last point of consideration, I do not understand why each language creates its own package manager. I spoke with a Gentoo Haskell developer who recommended installing packages from dev-haskell as opposed to from cabal, however a lot of Haskell projects expect you to use cabal.
In some cases this provides novel functionality, e.g. Python's virtual environments, but most of the time it seems like the default behavior is to install to /.
But if I have to pick, which one is right? I would like agner to be added (if it actually exists) as I can pragmatically recognize people find them to be useful, but I am still confused and would prefer to use portage.