From 99cc03399059853dd8699cae5752e8122cb715f1 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Wed, 7 Dec 2011 19:10:38 -0600 Subject: Rename KDEHOME and KDEDIR --- kconf_update/README.kconf_update | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'kconf_update') 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 -- cgit v1.2.3