diff options
author | Darrell Anderson <[email protected]> | 2012-11-04 01:46:07 -0500 |
---|---|---|
committer | Darrell Anderson <[email protected]> | 2012-11-04 01:46:07 -0500 |
commit | e256298e9d1d5f3f7fb5660f0ca33ea8489acd08 (patch) | |
tree | c1cb331fe9ebe18846c72c565342b82ce824877d /kconf_update/README.kconf_update | |
parent | 55c0d54a9863b438be2949a4629ec3fb0a307fe4 (diff) | |
download | tdelibs-e256298e9d1d5f3f7fb5660f0ca33ea8489acd08.tar.gz tdelibs-e256298e9d1d5f3f7fb5660f0ca33ea8489acd08.zip |
Fix references to user profile directory.
Diffstat (limited to 'kconf_update/README.kconf_update')
-rw-r--r-- | kconf_update/README.kconf_update | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/kconf_update/README.kconf_update b/kconf_update/README.kconf_update index 32c087c01..c8229c735 100644 --- a/kconf_update/README.kconf_update +++ b/kconf_update/README.kconf_update @@ -211,9 +211,9 @@ The easiest is to not install the kconf_update script in the first place, but manually call it through a pipe. If you want to test the update script for your application KHello's config file khellorc, you can test by using - cat ~/.kde/share/config/khellorc | khello_conf_update.sh + cat ~/.trinity/share/config/khellorc | khello_conf_update.sh -(assuming khello_conf_update.sh is the kconf_update script and ~/.kde is your +(assuming khello_conf_update.sh is the kconf_update script and ~/.trinity is your $TDEHOME). This is easier than making install every time, but has the obvious downside that you need to 'parse' your script's output yourself instead of letting kconf_update do it and check the resulting output file. |