Plugin paths stored in ckeditor settings cause problems if you move modules.

We recently re-structured our modules folder for contrib/custom etc. This included moving ckeditor_link from sites/all/modules/ckeditor_link to sites/all/modules/contrib/ckeditor_link. Registry Rebuild dealt with updating all the paths. However, the settings in ckeditor_settings.settings store the complete path at the point of saving in admin due to ckeditor_load_plugins():

        $arr['ckeditor_link'] = array(
            'name' => 'drupal_path',
            'desc' => t('Support for the CKEditor Link module'),
            'path' => $base_path . drupal_get_path('module', 'ckeditor_link') . '/plugins/link/',
            'buttons' => FALSE,
            'default' => 't'
        );

I wonder if it's be better to store module and path relative to the module, rather than the entire path, and then to convert that on render. That way you wont end up storing out of date paths.