The actual stable version is 2.4.1, and the moonlight version in portage tree is 2.3 (maybe this also could fix #340375)
I hope upstream have improved its building as it was really a mess before, thanks for notifying the bump
I don't know how to handle this in ebuild: - A specific mono version needs to be configured with special options, compiled and installed under build directory. But this installation cannot be installed in real system. - After that, moonlight runs configure and builds against that special mono version. The problem is how to handle this as this would require to run configure/make/make_install for mono before building moonlight, and I don't know what phase should be used for that. Any ideas?
If the rest of dotnet team agrees, I would vote for moving moonlight to maintainer-needed as this is a headache to maintain and, at least, browser plugin is easily installable from upstream site :-/
www-plugins/moonlight was finally removed