Upgrades pluging

OK. I am trying to figure out how to take larger plugins, like gallery plugins, that are not MU specific, and run out of the normal /plugins directory. Many of these themes assume that they reside in the /plugins directory and I am not keen on editing plugins if I don't have too.

I wrote a little plugin that I put into the upgrades-plugin directory. It allows me to keep the big plugin in the regular /plug-ins directory, but it kinda activates it when the user upgrades (currently uses a php include() statement). It keeps me from having to edit individual plugins plus lets the pluging remain where it was installed.

I was hoping someone could take a look at the code and see why this really shouldn't work (although it does). If it looks good, it is a cool way to add new plugins to the upgrades plugin without having to worry if it is 'mu specific'.

Plugin Name: Inlcude Upgrade Plugin
Plugin URI: http://rdgriffin.com/wordpress
Description: Inlcude Upgrade Plugin
Version: 0.0.1
Author: Robert Griffin
Author URI: http://rdgriffin.com/wordpress

//register premium features
upgrades_register_feature('lazyc87704c8391e2ed74e1a9c3830e986c0', 'My Gallery', 'Add advanced Gallery.');

//load premium features
if (upgrades_active_feature('lazyc87704c8391e2ed74e1a9c3830e986c0') == 'active'){
include ABSPATH . PLUGINDIR . '/advanced-gallery/advanced-gallery.php';

I think it would be better if I actually used Wordpress's plug-in activate so I could see if the plug-in was activated from the plugins list in the blog. While this works and the gallery is running when the user upgrades, it still shows as deactivated when visiting plug-ins in manage > plugins (when using plugin commander. Haven't looked at regular admin > plugins since I don't have that activated). But I was unsure how to do this (ok, I was too lazy to look into the codex).

Take a look and let me know if this is dangerous, bad, stupid or what.