Protect fckeditor.config.js from being overwritten by mistake

It's great to be able to customize FCKeditor through fckeditor.config.js, but the placement of the file seems to me to make it very easy to overwrite by mistake (like when updating the module to a new version). Apparently Drupal's settings.php file had that problem. I know I overwrote a few of those with the default settings.php in Drupal 5. Now in Drupal 6 the file is called default.settings.php and renamed settings.php by the installer. That way you can't overwrite your server settings by uploading a fresh distribution of core. I wonder if a similar approach couldn't be adopted with fckeditor.config.js. Call it default.fckeditor.config.js in the download package and have the installation routine rename it. Or--an option I'm even fonder of--what if the module checked for the presence of fckeditor.config.js in the theme folder and used it if it existed the way the templating system does for tpl.php files? That would keep things all nicely packaged and portable. Whatever the final solution, I think it would be good to do something.