Now, someone has probably already thought of this, but...
I was thinking the other day how cumbersome (ok, it's not _that_ cumbersome) it is to deal with config files each time I update my system, and got the idea in my head that portage should use cvs (or equivalent) to track changes to config files and apply those changes to new versions of config files that come out. It would require that everyone have cvs installed locally, and it wouldn't be all that great for existing systems (cause you'd have to have the original config file in cvs first), but for a new/future systems I think that it would make portage more seamless when updating.
Thoughts, comments, flames welcome. Dan
NOTE: For those that don't know (and on this list there probably aren't any), cvs has an easy way to track changes made to third party products and when you get a new version of a third party product you can tell it to apply your changes to the new version. So if you think of the ebuilds config files as the third party products then you can take your changes from the original version of the config file and apply them to the new version of the config file. Sometimes it's can't do it and you have to manually merge the files, but at least it would get rid of a lot of time trying to get rid of all the config files that just change the header information, and should make it lots easier for files where you changed the defaulted values.
-- [email protected] mailing list
