summaryrefslogtreecommitdiffstats
path: root/kconf_update
diff options
context:
space:
mode:
authorDarrell Anderson <humanreadable@yahoo.com>2012-11-04 01:46:07 -0500
committerSlávek Banko <slavek.banko@axis.cz>2012-11-09 01:57:38 +0100
commit205b3397710e08554fe2be67dee5fa4876e8d234 (patch)
tree28a5fc9e5fb7519f0063310cf0f70f521244fdec /kconf_update
parent03929452275f29cf2c2cb7b331be898838506e14 (diff)
downloadtdelibs-205b3397710e08554fe2be67dee5fa4876e8d234.tar.gz
tdelibs-205b3397710e08554fe2be67dee5fa4876e8d234.zip
Fix references to user profile directory.
(cherry picked from commit e256298e9d1d5f3f7fb5660f0ca33ea8489acd08)
Diffstat (limited to 'kconf_update')
-rw-r--r--kconf_update/README.kconf_update4
1 files changed, 2 insertions, 2 deletions
diff --git a/kconf_update/README.kconf_update b/kconf_update/README.kconf_update
index 14d50ad66..25a0d8f98 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
$KDEHOME). 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.