[okular] [Bug 385468] "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped."

[Matthew Dawson]

https://bugs.kde.org/show_bug.cgi?id=385468

--- Comment #6 from Matthew Dawson <matthew at mjdsystems.ca> ---
(In reply to Albert Astals Cid from comment #5)
> (In reply to Matthew Dawson from comment #4)
> > 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.
> 
> For my application there's no such thing as "KDE4" configuration files, they
> are just configuration files, and ideally one should be able to go from an
> old version (based on kdelibs4, irrelevant) where the okular.upd had not
> been run to the new version (based on KF5, irrelevant) and get okular.upd
> run and then the config be migrated to the new location.
> 
> As I understand you're saying that this is impossible and thus i basically
> should just remove the .upd file?

The situation may have changed since this was brought up.  At the time, you'd
use the Kdelibs4Migration class (
https://api.kde.org/frameworks/kcoreaddons/html/classKdelibs4Migration.html )
to move the file to the new KF5 location (using the XDG directory instead of
the .kde directory).  The upd file wasn't used for that purpose.

If using the upd file is now the recommended way to do the migration, then you
can ignore my suggestion.  I'm not sure though the upd file is flexible to
handle custom kde prefixes that Kdelibs4Migration does.

-- 
You are receiving this mail because:
You are the assignee for the bug.