Development/Tools/Using kconf update: Difference between revisions

From KDE TechBase
m (Insert link to KDED)
(Extract most example sections and other tutorial-like sections to Development/Tutorials/Updating_KConfig_Files, so this page contains less read-once information.)
Line 1: Line 1:
{{Being_Edited}}
== Introduction ==
== Introduction ==
'''kconf_update''' is a tool designed to update KConfig configuration files.
'''kconf_update''' is a tool designed to update KConfig configuration files.
Line 16: Line 14:
kconf_update is primarily used to move configuration entries from one place to another, but can also be used to modify the configuration data itself.
kconf_update is primarily used to move configuration entries from one place to another, but can also be used to modify the configuration data itself.


=== How it works ===
=== How to use ===
Applications can install so called ''update files'' in {{path|${KDE_INSTALL_KCONFUPDATEDIR}}}.
To use kconf_update in your application, you only need to write an update file and install it in {{path|${KDE_INSTALL_KCONFUPDATEDIR}}}.
An update file has {{path|.upd}} as extension, and contains instructions for transferring and converting configuration information.
An example update file is in the section [[#Example update file]].
Update files are separated into sections, and each section has an unique ID.
 
kconf_update is started automatically when [https://api.kde.org/frameworks/kded/html/index.html '''KDED'''] detects a new update file in the above mentioned location.
kconf_update will first check in its own configuration file ({{path|kconf_updaterc}}, usually located in {{path|~/.config/}}) which sections of the update file haven’t been processed yet.
When a section has been processed, its ID is stored in {{path|kconf_updaterc}} and the affected configuration files, to make sure it will not be processed again.


If you overwrite an existing update file with a new version that contains a new section, only the update instructions from this new section will be processed.
If your application depends on KDED, kconf_update will be started automatically when the update file is installed.
 
Otherwise, you can start it manually using <code>KConfig::checkUpdate()</code>.
If your application does not depend explicitely on KDED (e. g. if your target platform isn’t Linux or FreeBSD), kconf_update may not be started automatically.
You can start it manually using <code>KConfig::checkUpdate()</code>.
Note that kconf_update might process your update multiple times simultaneously in this case.
Note that kconf_update might process your update multiple times simultaneously in this case.
This can cause problems if your update file uses the <code>Script=</code> command.
This can cause problems if your update file uses the <code>Script=</code> command.
See the [[#Note on side effects]] section for more details.
See the [[#Note on side effects]] section for more details.
=== How to use ===
To use kconf_update in your application, you only need to write an update file and install it in the right place.
An example update file is in the section [[#Minimal example update file]].
Add the following lines to your {{path|CMakeLists.txt}}:
<syntaxhighlight lang="cmake">
# Extra CMake Modules (ECM) defines variables like KDE_INSTALL_KCONFUPDATEDIR:
find_package(ECM ${KF5_REQUIRED_VERSION} CONFIG REQUIRED)
# Makes your application compile with KConfig:
find_package(KF5 ${KF5_REQUIRED_VERSION} REQUIRED COMPONENTS
    Config
    [...]
)
# Installs the update file in the right place:
install(FILES okular.upd DESTINATION ${KDE_INSTALL_KCONFUPDATEDIR})
</syntaxhighlight>


{{Warning|
{{Warning|
Line 57: Line 28:
See the [[#Testing update files]] section.
See the [[#Testing update files]] section.
}}
}}
=== Minimal example update file ===
Imagine your need to change the name of one entry in your configuration file.
This happened in '''Okular''', and this is the content of {{path|${KDE_INSTALL_KCONFUPDATEDIR}/okular.upd}}:
<syntaxhighlight lang="ini">
#Configuration update for Okular
Version=5
#Convert user-defined annotation tools to quick annotation tools
Id=annotation-toolbar
File=okularpartrc
Group=Reviews
Key=AnnotationTools,QuickAnnotationTools
</syntaxhighlight>
It will change the contents of {{path|okularpartrc}} from e. g.:
<syntaxhighlight lang="ini">
[Reviews]
AnnotationTools=highlight,underline
</syntaxhighlight>
to:
<syntaxhighlight lang="ini">
[$Version]
update_info=okular.upd:annotation-toolbar
[Reviews]
QuickAnnotationTools=highlight,underline
</syntaxhighlight>
Note that it changed the name of the <code>AnnotationTools</code> entry in the <code>Reviews</code> group, and added a new <code>$Version</code> group to mark the <code>annotation-toolbar</code> update as done.
To try this example, see the [[#Testing update files]] section.


== Testing update files ==
== Testing update files ==
You can run kconf_update manually on a specific update file, to see how it will process it.
You can run kconf_update manually on a specific update file, to see how it will process it.
If your update file is called {{path|myUpdate.upd}}, you would run this command:


First, you need to locate your kconf_update executable.
{{Input|<nowiki>
(Try e. g. <code>locate kconf_update</code>.)
/usr/lib/kf5/kconf_update --debug --testmode path/to/myUpdate.upd
If you can’t locate it, you can also compile it from the KConfig repository.
</nowiki>}}
Let’s assume your kconf_update executable is located at {{path|/usr/lib/kf5/kconf_update}}.


kconf_update offers the command line options <code>--debug</code> and <code>--testmode</code>.
<code>--testmode</code> activates <code>QStandardPaths::setTestModeEnabled()</code>, so kconf_update will not update your actual configuration files, but files you have placed in a certain test directory.
<br/><code>--debug</code> enables helpful debugging output on the command line.
<br/><code>--testmode</code> activates <code>QStandardPaths::setTestModeEnabled()</code>, so kconf_update will not update your actual configuration files, but files you have placed in a certain test directory.
See the <code>QStandardPaths::GenericConfigLocation</code> documentation for your platform.
See the <code>QStandardPaths::GenericConfigLocation</code> documentation for your platform.
Let’s assume this test directory is {{path|~/.qttest/config/}}.
Now place your update file and a test configuration file in your working directory.
Assuming you are testing the file from [[#Minimal example update file]], you run:
{{Input|1=<nowiki>
mkdir -p ~/.qttest/config/
cp okularpartrc ~/.qttest/config/
/usr/lib/kf5/kconf_update --debug --testmode ./okular.upd
</nowiki>}}
Then you should get an output like:
{{Output|1=<nowiki>
Automatically enabled the debug logging category kf.config.kconf_update
kf5.kconfig.update: Checking update-file "./okular.upd" for new updates
kf5.kconfig.update: "okular.upd" : Found new update "annotation-toolbar"
kf5.kconfig.update: "okular.upd" : Updating "okularpartrc" : "Reviews" : "QuickAnnotationTools" to "highlight,underline"
kf5.kconfig.update: "okular.upd" : Removing "okularpartrc" : "Reviews" : "AnnotationTools" , moved.
</nowiki>}}
Now you should open {{path|~/.qttest/config/okularpartrc}} to verify that the update was performed correctly.
If you see the new <code>$Version</code> group there, but <code>AnnotationTools</code> was not renamed, the update was performed, but something is wrong with your update instructions.
If you don’t see the new <code>$Version</code> group, the update didn’t affect the correct configuration file.
{{Tip|
For the first tests, it is convenient to write a configuration file that contains only the entries you are interested in (like in [[#Minimal example update file]]).
But you should also perform a test with a configuration file from an actual installation of your application.
}}
{{Tip|
If you want to test the update file again, you need to restore an old version of the configuration file first.
Additionally, you need to open {{path|kconf_updaterc}}, and remove the <code>okular.upd</code> group, otherwise kconf_update will skip your update file.
Since Frameworks version KF 5.76, kconf_update will ignore {{path|kconf_updaterc}} while in <code>--testmode</code>
}}
=== Testing installed update files ===
When you think your update file works fine, you may try to completely compile and install the new version of your application.
After you have run e. g. <code>make install</code>, your update file should show up in the correct directory.
KDED will detect this, and run kconf_update.
Your installed configuration file should now be updated, and you can open it to verify the update.
However, if you find problems now, you probably want to let the update run again.
If you install a new update file, KDED will run kconf_update again, but kconf_update will not perform the update.
What you need to do is:
* Restore an old version of the configuration file, so there is something to update again. The old version shouldn’t contain the <code>$Version</code> group.
* Locate {{path|kconf_updaterc}} (e. g. with the command <code>locate kconf_updaterc</code>), and remove the group named by your update file.
Now, kconf_update will process the update again, as soon as you overwrite the update file.
Since <code>make install</code> won’t overwrite the file with itself, you need to manually delete it first.
You can also try to run kconf_update manually, e. g. with the command <code>/usr/lib/kf5/kconf_update --debug</code> (without other arguments).
==== Debug output while running in the background ====
Because kconf_update will now run in the background, you will not directly get debug output.
After KDE Frameworks 5.57, debug output goes through the category <code>kf.config.kconf_update</code>.
If this category is enabled, debug output will be printed to ''stderr'' and consequently end up in {{path|xsession-errors}} or {{path|wayland-errors}}.
See the <code>QLoggingCategory</code> documentation for how to enable this logging category.
Probably you can add the following group to a configuration file like {{path|/usr/share/qt5/qtlogging.ini}}:
{{Input|1=<nowiki>
[Rules]
kf.config.kconf_update=true
</nowiki>}}


If Qt was built with support for logging to system log facilities (such as systemd-journald), the output may be found there instead.
See [[Development/Tutorials/Updating_KConfig_Files#Testing_update_files]] for more information on testing update files.
Before 5.57, the output was always sent to ''stderr'' and may be found in the aforementioned errors files.


== File format of the update file ==
== File format of the update file ==
Each line of the update file can contain a command (like <code>File=okularpartrc</code>) or a comment (like <code># Hello!</code>).
Each line of the update file can contain a command (like <code>File=okularpartrc</code>) or a comment (like <code># Hello!</code>).
Commands are processed sequentially from top to bottom.
Commands are processed sequentially from top to bottom.
=== Description of the minimal example update file ===
In the section [[#Minimal example update file]], we see the following lines:
; <code>#Configuration update for Okular</code>
: Empty lines and lines that start with <code>#</code> are considered comments.
; <code>Version=5</code>
: Specifies that this update file is written for the KF5 version of kconf_update.
: Every update file must start with this command.
; <code>Id=annotation-toolbar</code>
: Starts an update section called ''annotation-toolbar''.
; <code>File=okularpartrc</code>
: Tells kconf_update which configuration file shall be affected.
; <code>Group=Reviews</code>
: Tells kconf_update that it shall operate on the ''Reviews'' group of the configuration file.
; <code>Key=AnnotationTools,QuickAnnotationTools</code>
: Tells kconf_update that it shall read from the entry ''AnnotationTools'' and write to the entry ''QuickAnnotationTools''.
: In this case, this causes the entry to be renamed.


=== Update file structure ===
=== Update file structure ===
Line 326: Line 169:


Alternatively, you can use “compiled scripts”, which are executable binaries installed in {{path|${KDE_INSTALL_LIBDIR}/kconf_update_bin/}}. You can e. g. write your update script in C++ and use all the Qt API and other libraries you need, and compile and install the binary together with your application.
Alternatively, you can use “compiled scripts”, which are executable binaries installed in {{path|${KDE_INSTALL_LIBDIR}/kconf_update_bin/}}. You can e. g. write your update script in C++ and use all the Qt API and other libraries you need, and compile and install the binary together with your application.
=== Example interpreted update script ===
Imagine you want to switch from a ''DoNotUseTabs'' configuration entry to a ''UseTabs'' configuration entry.
This can be easily done using this small Python script:
<syntaxhighlight lang="python">
import fileinput
for line in fileinput.input():
    if line.startswith("DoNotUseTabs=false"):
        print("UseTabs=true")
    if line.startswith("DoNotUseTabs=true"):
        print("UseTabs=false")
print("# DELETE DoNotUseTabs")
</syntaxhighlight>
Your update file could look like this:
<syntaxhighlight lang="ini">
Version=5
Id=no-more-double-negation-2020
File=myApprc
Group=UserInterface
Script=myApp_no_more_double_negation_2020.py,python3
</syntaxhighlight>
Your CMakeLists.txt could look like this:
<syntaxhighlight lang="cmake">
[...]
find_package(ECM ${KF5_REQUIRED_VERSION} CONFIG REQUIRED)
[...]
find_package(KF5 ${KF5_REQUIRED_VERSION} REQUIRED COMPONENTS
    Config
    [...]
)
[...]
install(FILES conf/update/myApp_configFiles.upd DESTINATION ${KDE_INSTALL_KCONFUPDATEDIR})
install(FILES conf/update/myApp_no_more_double_negation_2020.py DESTINATION ${KDE_INSTALL_KCONFUPDATEDIR})
</syntaxhighlight>
Don’t forget that your appliation now depends on python3.
=== Example compiled update script ===
Imagine your application made the state of a KActionMenu user configurable.
Because you changed to the new QToolButton::ToolButtonPopupMode API, you need to migrate from the old ''delayed'' and ''stickyMenu'' entries to the new ''popupMode'' entry.
You can do that with the following compiled update script, which uses the KConfig framework directly:
<syntaxhighlight lang="cpp">
#include <KConfig>
#include <KConfigGroup>
#include <QTemporaryFile>
#include <QTextStream>
int main(int argc, char **argv)
{
    // Create a KConfig object from stdin.
    QFile inputFile;
    inputFile.open(stdin, QIODevice::ReadOnly);
    QTemporaryFile inputFileForKConfig("popupmode_api_tmp");
    inputFileForKConfig.open();
    inputFileForKConfig.write(inputFile.readAll());
    inputFileForKConfig.close();
    KConfig inputConfig(inputFileForKConfig.fileName(), KConfig::SimpleConfig);
    // Create a text stream to stdout.
    QTextStream outputStream(stdout, QIODevice::WriteOnly);
    // Unify delayed and stickyMenu.
    // delayed => 0 (DelayedPopup)
    // !delayed && stickyMenu => 2 (InstantPopup)
    // !delayed && !stickyMenu => 1 (MenuButtonPopup) (defined as default with KConfigXT)
    KConfigGroup rootGroup = inputConfig.group("");
    bool old_delayed = rootGroup.readEntry<bool>("delayed", true);
    bool old_stickyMenu = rootGroup.readEntry<bool>("stickyMenu", true);
    int new_popupMode = (old_delayed) ? 0 : (old_stickyMenu) ? 2 : 1;
    if (new_popupMode != 1) {
        outputStream << "popupMode=" << new_popupMode << Qt::endl;
    }
    outputStream << "# DELETE delayed" << Qt::endl;
    outputStream << "# DELETE stickyMenu" << Qt::endl;
    return 0;
}
</syntaxhighlight>
Your update file could look like this:
<syntaxhighlight lang="ini">
Version=5
Id=toolbuttonpopupmode-api-2020
File=myApprc
Group=ActionMenuState
Script=myApp-toolbuttonpopupmode-api-2020
</syntaxhighlight>
Your CMakeLists.txt could look like this:
<syntaxhighlight lang="cmake">
[...]
find_package(ECM ${KF5_REQUIRED_VERSION} CONFIG REQUIRED)
[...]
find_package(KF5 ${KF5_REQUIRED_VERSION} REQUIRED COMPONENTS
    Config
    [...]
)
[...]
install(FILES myApp_configFiles.upd DESTINATION ${KDE_INSTALL_KCONFUPDATEDIR})
add_executable(myApp-toolbuttonpopupmode-api-2020 conf/update/scripts/popupmode.cpp)
target_link_libraries(myApp-toolbuttonpopupmode-api-2020
    KF5::ConfigCore
)
install(TARGETS myApp-toolbuttonpopupmode-api-2020 DESTINATION ${KDE_INSTALL_LIBDIR}/kconf_update_bin/)
</syntaxhighlight>
Because you don’t need an interpreter, you didn’t add any dependency to your application.
=== Testing external update scripts ===
The first step to test external update scripts is to call them directly, and feed them with your configuration files.
For example, you can test the script from [[#Example interpreted update script]] with this command:
{{Input|1=<nowiki>
cat myApprc_UserInterface | python3 myApp_no_more_double_negation_2020.py
</nowiki>}}
If the script works correctly, you should get output like this:
{{Output|1=<nowiki>
UseTabs=true
# DELETE DoNotUseTabs
</nowiki>}}
The second step is to test your update file together with the script.
This means, you need to place the script file in a place where kconf_update will find it while in <code>--testmode</code>.
kconf_update will look for the script in <code>QStandardPaths::GenericDataLocation</code>.
Let’s assume this path is {{path|~/.qttest/share/}}, then you need to place your script in {{path|~/.qttest/share/kconf_update/}}.
Place your update file, your update script, and your configuration file in your working directory, and run:
{{Input|1=<nowiki>
mkdir -p ~/.qttest/config/
cp myApprc ~/.qttest/config/
mkdir -p ~/.qttest/share/kconf_update/
cp myApp_no_more_double_negation_2020.py ~/.qttest/share/kconf_update/
/usr/lib/kf5/kconf_update --debug --testmode ./myApp_configFiles.upd
</nowiki>}}
You should get an output like:
{{Output|1=<nowiki>
Automatically enabled the debug logging category kf.config.kconf_update
kf.config.kconf_update: Checking update-file "./myApp_configFiles.upd" for new updates
kf.config.kconf_update: "demo9.upd" : Found new update "no-more-double-negation-2020"
kf.config.kconf_update: "demo9.upd" : Running script "myApp_no_more_double_negation_2020.py"
kf.config.kconf_update: Script input stored in "/tmp/kconf_update.lKlJpe"
kf.config.kconf_update: About to run "/usr/bin/python3"
kf.config.kconf_update: Script contents is:
"[...]"
kf.config.kconf_update: Successfully ran "/usr/bin/python3"
kf.config.kconf_update: Script output stored in "/tmp/kconf_update.CCeaBP"
kf.config.kconf_update: Script output is:
"UseTabs=true\n# DELETE DoNotUseTabs\n"
kf.config.kconf_update: "demo9.upd" : Script removes "myApprc" : ("UserInterface") : "DoNotUseTabs"
</nowiki>}}
If you want to test compiled update scripts, the workflow is the same, except that you may place your compiled update script in one of your {{path|$PATH}} directories instead.


=== Note on side effects ===
=== Note on side effects ===
Line 520: Line 191:
If it is a problem, you should consider to use multiple sections with only one ''File='' command each.
If it is a problem, you should consider to use multiple sections with only one ''File='' command each.


== Advanced example update file ==
== Example update file ==
<syntaxhighlight lang="ini">
<syntaxhighlight lang="ini">
Version=5
Version=5
Line 552: Line 223:


Finally it removes the entire ''KDE'' group from the {{path|kioslaverc}} file.
Finally it removes the entire ''KDE'' group from the {{path|kioslaverc}} file.
== Further example update files ==
Another way to learn how to write scripts and update files is to look at existing ones.
With the following command, you can look which applications on your system have installed update files:
{{Input|1=<nowiki>
locate kconf_update
</nowiki>}}
You can also search through various KDE projects with this link:
https://lxr.kde.org/search?_filestring=.%2B%5C.upd%5Cz&_advanced=1


== Common Problems ==
== Common Problems ==

Revision as of 15:54, 29 October 2020

Introduction

kconf_update is a tool designed to update KConfig configuration files.

What it does

Applications sometimes need to rearrange the way configuration options are stored.

To avoid losing the old configuration, the application can look up both the old and the new configuration, and then decide which one to use. But this means that the application contains additional code, which deals only with configuration of the past, and is only used once.

kconf_update addresses this problem by offering a framework to update configuration files, without adding complexity to the application itself.

kconf_update is primarily used to move configuration entries from one place to another, but can also be used to modify the configuration data itself.

How to use

To use kconf_update in your application, you only need to write an update file and install it in ${KDE_INSTALL_KCONFUPDATEDIR}. An example update file is in the section #Example update file.

If your application depends on KDED, kconf_update will be started automatically when the update file is installed. Otherwise, you can start it manually using KConfig::checkUpdate(). Note that kconf_update might process your update multiple times simultaneously in this case. This can cause problems if your update file uses the Script= command. See the #Note on side effects section for more details.

Warning
Before you deploy update files to your users, you should verify that they do what you want. Otherwise you will probably get bug reports, but you already missed your change to fix them. See the #Testing update files section.


Testing update files

You can run kconf_update manually on a specific update file, to see how it will process it. If your update file is called myUpdate.upd, you would run this command: 

/usr/lib/kf5/kconf_update --debug --testmode path/to/myUpdate.upd

--testmode activates QStandardPaths::setTestModeEnabled(), so kconf_update will not update your actual configuration files, but files you have placed in a certain test directory. See the QStandardPaths::GenericConfigLocation documentation for your platform.

See Development/Tutorials/Updating_KConfig_Files#Testing_update_files for more information on testing update files.

File format of the update file

Each line of the update file can contain a command (like File=okularpartrc) or a comment (like # Hello!). Commands are processed sequentially from top to bottom.

Update file structure

Update files are structured as follows:

  • Version=5 (required)
  • any number of update sections, each started by an Id= command
    • any number of Script= and ScriptArguments= commands
    • or any number of File= commands, followed by:
      • any number of Group=, Key=, AllKeys, RemoveGroup=, RemoveKey=, Options=, Script=, ScriptArguments= commands
      • AllGroups (optional)

Update file command reference

All commands are case-sensitive. Commas are used to separate parameters, and may not occur as part of any parameter. Parameters in square brackets are optional. Parameters are referenced in angle brackets, sometimes parameters of preceeding commands are referenced. (Square brackets and angle brackets are not written in the actual update file.)

The following commands are available:

Version=5
This must be the first command in any update file.
Specifies which KDE Frameworks version this update file targets. At the time of writing the only valid value is 5, meaning modern (KDE Frameworks 5) kconf_update binaries will process the file. A file with Version=5 may still be run on older kconf_updates!
Id=<id>
Starts a new update section. All commands until the next Id= command are processed as part of this section. If <id> is stored in kconf_updaterc, this section will be skipped. When this section has been processed, <id> will be stored in kconf_updaterc.
<id> has to be unique. You should give your section a name that describes why this update necessary. You can also include the year of your changes, like in Id=annotation-toolbar-2020.
File=<oldfile>[,<newfile>]
Specifies that configuration information is read from <oldfile> and written to <newfile>. If you only specify <oldfile>, the information is read from as well as written to <oldfile>.
If <oldfile> contains the <id> of the current section, the current section will be skipped. Otherwise, <id> is stored in <oldfile> and <newfile>.
If <oldfile> does not exist at the time kconf_update first checks, the current section will be skipped.
Also note the #Updating multiple files per section section.
Group=<oldgroup>[,<newgroup>]
Specifies that configuration information is read from the group <oldgroup> and written to <newgroup>. If you only specify <oldgroup>, the information is read from as well as written to <oldgroup>.
You can use <default> to select the top-level group.
Key=<oldkey>[,<newkey>]
Moves the configuration entry <oldkey> from <oldfile>/<oldgroup> to <newfile>/<newgroup>.
If you specify <newkey>, the entry is additionally renamed.
If you did not specify <newfile> nor <newgroup> nor Options=copy, the entry is only renamed.
AllGroups
Moves all groups (including all entries) from <oldfile> to <newfile>.
Note that the top-level group is not included. To include the top-level group, you need to use the AllKeys command additionally.
AllKeys
Moves all entries from <oldgroup> to <newgroup>.
RemoveGroup=<oldgroup>
Removes <oldgroup> from <oldfile>.
This can be used to remove obsolete entries or to force a revert to default values.
RemoveKey=<oldkey>
Removes <oldkey> from <oldfile>/<oldgroup>.
This can be used to remove an obsolete entriy or to force a revert to default values.
Options=<option1>, <option2>, ...
With this entry you can specify options that apply to the next Script=, Key=, AllKeys, or AllGroups command (only to the first). Note that Script= probably ignores the options, see the #Script output format section.
Possible options are:
copy
Copy the configuration item instead of moving it. This means that the configuration item will not be deleted from <oldfile> or <oldgroup>.
overwrite
Normally, configuration entries are not moved if an entry with the new name already exists. When this option is specified, any existing entries are overwritten.
Script=<_script>[,<interpreter>]
ScriptArguments=<arguments>
See the #Update script commands section.

Using external update scripts

kconf_update provides commands to move configuration information around, but it can not manipulate the configuration data itself. Using external, so called update scripts, configuration data can be manipulated through kconf_update.

The concept is that old configuration entries are piped into a script. The output of the script is then interpreted as new configuration entries, which are merged to <newfile> or <newgroup>.

It is also possible to use scripts outside the context of a File= command, then it will not get any input, and the output is ignored. See the section #Note on side effects about this.

Update script commands

The following two commands are available to run update scripts:

Script=<_script>[,<interpreter>]
Executes the script file <_script> using the command <interpreter>. If <interpreter> is not given, executes the compiled script file <_script> directly. You can not pass arguments with this command.
If in the context of a File= command, all groups of <oldfile> (excluding the top-level group) will be piped into the script. If in the context of a Group= command, all entries of <oldgroup> will be piped into the script. You can use Group=<default> to process top-level entries.
The output of <_script> is merged into <newfile> or <newgroup>.
ScriptArguments=<arguments>
<arguments> is passed to <_script> of the next Script= command (only to the first).
<arguments> is everything from the = sign to the end of the line. Escape sequences are not possible.
Note that you must specify ScriptArguments= before Script=.

Script output format

The output of the script is parsed as configuration file, and merged to <newfile> or <newgroup>. If in the context of File=, script output is merged to the top-level group of <newfile>. If in the context of Group=, the group context is initialized to <newgroup>.

These lines in the script output are recognized by kconf_update:

[<groupname>]
Sets the group context to <groupname>. This will not create a subgroup, even in the context of Group=.
You can use [<default>] to select the top-level group. However, this will not work in context of Group=.
<key>=<value>
Creates a new entry in the current group context.
Note that existing entries will probably not be overridden, even with Options=override specified.
# DELETE <key>
Deletes the entry <key> in the current group context, but from <oldfile>.
# DELETE [<group>]<key>
Deletes the entry <key> from the group <oldfile>/<group>.
Note that this can change the group context, you should explicitely set the group context afterwards.
# DELETEGROUP <group>
Deletes the whole group <group> (not a subgroup) from <oldfile>.
Note that this can change the group context, you should explicitely set the group context afterwards.

Providing the script files

Script files should be installed in ${KDE_INSTALL_KCONFUPDATEDIR}. You should install only actual scripts here, not binary executables.

You should choose a script language whose interpreter will be available on your target platform. E. g. if your target platforms include Windows, you should not use shell scripts.

Alternatively, you can use “compiled scripts”, which are executable binaries installed in ${KDE_INSTALL_LIBDIR}/kconf_update_bin/. You can e. g. write your update script in C++ and use all the Qt API and other libraries you need, and compile and install the binary together with your application.

Note on side effects

External update scripts can cause side effects. (E. g. rebuilding the database of another service.) This is an intended use case; you can use Script= in the context of Id=, then no script input or output is processed.

Nevertheless, you should be careful if you use update scripts for side effects. If your update scripts cause side effects, you probably want these side effects to happen at most once. KDED will run the update only once, but if KConfig::checkUpdate() is involved, this is not guaranteed.

Consider separating updates into two update files, where one update file performs only deterministic configuration file updates, and the other update file causes only side effects. This way, you can savely call KConfig::checkUpdate() to guarantee configuration file updates, while the other update file is processed at most once by KDED.

Updating multiple files per section

You can use multiple File= commands in the context of one Id= command, then this update section will sequentially update multiple files. This can be used to split a single configuration file into multiple configuration files, or to join multiple configuration files into a single configuration file.

However, in the latter case you will have different <oldfile> parameters. You should be aware that kconf_update will stop processing a section, when it encounters an <oldfile> which already has this update applied. In most cases, this shouldn’t be a problem. If it is a problem, you should consider to use multiple sections with only one File= command each.

Example update file

Version=5

Id=kde2.2
File=kioslaverc,kio_httprc

Group=Proxy Settings
Key=NoProxyFor
Key=UseProxy
Key=httpProxy,Proxy

Group=Cache Settings,Cache
Key=MaxCacheSize
Key=UseCache

Group=UserAgent
AllKeys

RemoveGroup=KDE

The above update file extracts config information from the file kioslaverc and stores it into the file kio_httprc.

It reads the keys NoProxyFor, UseProxy and httpProxy from the group Proxy Settings in the kioslaverc file. If any of these options are present they are written to the keys NoProxyFor, UseProxy and Proxy (!) in the group Proxy Settings in the kio_httprc file.

It also reads the keys MaxCacheSize and UseCache from the group Cache Settings in the kioslaverc file and writes this information to the group Cache (!) in the kio_httprc file.

Then it takes all keys in the UserAgent group of the file kioslaverc and moves then to the UserAgent group in the kio_httprc file.

Finally it removes the entire KDE group from the kioslaverc file.

Common Problems

kconf_update refuses to update an entry
If you change the value of an entry without changing the key or file, make sure to tell kconf_update that it should overwrite the old entry by adding Options=overwrite.
Retrieved from "https://techbase.kde.org/index.php?title=Development/Tools/Using_kconf_update&oldid=106750"