summaryrefslogtreecommitdiffstats
path: root/kconf_update/README.kconf_update
diff options
context:
space:
mode:
Diffstat (limited to 'kconf_update/README.kconf_update')
-rw-r--r--kconf_update/README.kconf_update6
1 files changed, 3 insertions, 3 deletions
diff --git a/kconf_update/README.kconf_update b/kconf_update/README.kconf_update
index 14d50ad66..385f3185e 100644
--- a/kconf_update/README.kconf_update
+++ b/kconf_update/README.kconf_update
@@ -27,7 +27,7 @@ How it works
============
Applications can install so called "update files" under
-$KDEDIR/share/apps/kconf_update. An update file has ".upd" as extension and
+$TDEDIR/share/apps/kconf_update. An update file has ".upd" as extension and
contains instructions for transferring/converting configuration information
from one place to another.
@@ -214,7 +214,7 @@ your application KHello's config file khellorc, you can test by using
cat ~/.kde/share/config/khellorc | khello_conf_update.sh
(assuming khello_conf_update.sh is the kconf_update script and ~/.kde is your
-$KDEHOME). This is easier than making install every time, but has the obvious
+$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.
@@ -235,7 +235,7 @@ file's entry, 'make install', and kconf_update will happily run your script
again, without you having to increase the version number.
If you want to know what kconf_update has been up to lately, have a look
-at $KDEHOME/share/apps/kconf_update/update.log
+at $TDEHOME/share/apps/kconf_update/update.log
Common Problems