Comment 2 for bug 324168

OK. This should really, really, be fixed, because it means that updates to the gnome-do-plugins package are worthless - the only way an updated plugin can be used is if:
a) If the new plugin has a higher mono.addins version number, and this is not automatic, or
b) If core starts looking for plugins in a different place (plugins-0.8.1.3 versus plugins-0.8.1.2), or
c) If the user deletes ~/.local/share/gnome-do/plugins-*

I should look at it, but it'd be *great* if someone else did it before me!