Should the package attempt to clean this up (and if so is there a better method than unconditionally deleting those directories), or is permanently leaving this behind (to become more and more obsolete, and potentially be read by users looking for the current documentation) the best that can be safely done?
Personally, I would be tempted to add the cleanup code, then remove it again in a couple of months. That should clean up the majority of systems, while not leaving aggressive cleanup code in a stable release.
