As per reference to
http://drupal.org/node/848740#comment-3253602
http://drupal.org/node/848740#comment-3254002
The admin interface is also a good idea. I would like to share my point about the one I've suggested hook_update_N(). Yes, it can clutter the install file if we leave the previous hook_update_N(). Since we only call same routine every time a new include update is available, we can safely maintain a single instance of hook_update_N() without cluttering the install file. The update system is only concern with the largest N. In my opinion, this is more semantic approach updating the variable table, additionally the user will never neglect to update the include list variable because of update system's persistent update attention message.
Comments
Comment #1
ckngI believe this is no longer relevant.