MonoDevelop released 2.2.
new version: http://monodevelop.com/Download/MonoDevelop_2.2.1_Released
Monodevelop 2.2.1 now is in portage but its plugins are not in portage, also in the post install message it says : "These optional plugins currently exist:" " - dev-util/monodevelop-boo" " - dev-util/monodevelop-java" " - dev-util/monodevelop-database" " - dev-util/monodevelop-debugger-gdb" " - dev-util/monodevelop-debugger-mdb" " - dev-util/monodevelop-vala" "To enable their (self-explanatory) functionality, just emerge them." "Read more here:" "http://monodevelop.com/" the last version in portage of each plugin is 2.1.1, 2.1.x series plugins requires a 2.1.x series monodevelop, so also the plugins bump is needed.
All plugins except monodevelop-java were bumped in portage
the current monodevelop-2.2.1 ebuild requires as of yet non existing plugin versions [ebuild N ] dev-util/monodevelop-vala-2.2 102 kB [ebuild N ] dev-util/monodevelop-java-2.2 USE="-debug" 44 kB [ebuild R ] dev-util/monodevelop-2.2.1 USE="subversion" 0 kB [nomerge ] dev-util/monodevelop-vala-2.2 [ebuild N ] dev-lang/vala-0.7.10 USE="coverage vapigen -test" 1,930 kB [blocks B ] <dev-util/monodevelop-java-2.2.1 ("<dev-util/monodevelop-java-2.2.1" is blocking dev-util/monodevelop-2.2.1) [blocks B ] <dev-util/monodevelop-vala-2.2.1 ("<dev-util/monodevelop-vala-2.2.1" is blocking dev-util/monodevelop-2.2.1) resulting from a copy and paste ebuild bump (i guess) RDEPEND="... !<dev-util/monodevelop-boo-${PV} !<dev-util/monodevelop-java-${PV} !<dev-util/monodevelop-database-${PV} !<dev-util/monodevelop-debugger-gdb-${PV} !<dev-util/monodevelop-debugger-mdb-${PV} !<dev-util/monodevelop-vala-${PV}" so if you have monodevelop-java or monodevelop-vala installed, then upgrading wont work.
07 Mar 2010; Peter Alfredsen <loki_val@gentoo.org> monodevelop-2.2.1.ebuild: Only block versions of language-modules <x.y, not <x.y.z
