That's great. :-) In the mean time, can you find some way to avoid a merge conflict for the Dapper -> Edgy transition? Here are some suggestions:
1) Assuming there are no new, compulsory configuration options, make it silently use the old config file, as it's upwardly compatible. 2) Use your knowledge of the config file format to do intelligent merging in the upgrade script (i.e. extract the user-specified config and stick it in the new file). 3) Silently use the new config file, and make the new version pop up up a message saying "Sorry, we lost your config. Please redo it.". Even 3), though it sucks, is better than the current situation. -- Dapper -> Edgy failure: sbackup configuration file has conflicts https://launchpad.net/bugs/63354 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
