https://bugs.kde.org/show_bug.cgi?id=385468
--- Comment #4 from Matthew Dawson <matt...@mjdsystems.ca> --- The original reason this was added was that KDE4 update scripts would get run by KF5, creating a configuration file. Then the KDE4 migration would not run, resulting in users losing their settings. This was put in at the time to stop that from occurring. Ideally, kconf_update would not create an empty configuration file for a migration just to note the migration had been run. However, there are some side effects to that change which make it more complicated to implement, and thus has not yet happened. Without fixing kconf_update, I don't want to back out the change as it still has a good reason. I also like that all the update files now have an enforced version header, which will make it easy to update the format in the future. And most configuration file update scripts should now have the header if required, so there will likely be more pain to revert it at this time. However, you do raise the good point that this requirement is not well communicated. That should definitely be fixed. Is there any particular place you would have expected this information to be present? Also, if the configuration update script is for KDE4 configuration files, you can skip putting a Version=5 header at the top. Instead, you can have the fully updated file migrated to the new configuration file location and start with a fresh update script for KF5. Or continue adding to the file. Whatever works best for okular. -- You are receiving this mail because: You are the assignee for the bug.
