Convert remaining references to kde3 (e.g. in paths) to trinity

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdenetwork@1248408 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
v3.5.13-sru
tpearson 13 years ago
parent 52497f5b05
commit d7c69d672c

@ -1,7 +1,7 @@
KGet 0.8.0-RC-1
==========
New working release of kget for kde3.
New working release of kget for trinity.
INSTALLATION
=============

@ -216,8 +216,8 @@ If you don't have write access to /etc/kderc, or if you want to use more
parallel builds of KDE and/or Kopete you need to rely on the environment
variables instead.
If $KDEDIRS currently points to /opt/kde3 and you installed Kopete
to /usr/local then you need to set $KDEDIRS to '/opt/kde3:/usr/local'.
If $KDEDIRS currently points to /opt/trinity and you installed Kopete
to /usr/local then you need to set $KDEDIRS to '/opt/trinity:/usr/local'.
You need to store this change in a file that is picked up by all shells
and for all users, like /etc/profile. The name of the preferred version
varies from system to system.
@ -225,9 +225,9 @@ varies from system to system.
As a last resort you can simply install Kopete in the same directory as
where your KDE resides by adding a flag to configure like
./configure --prefix=/opt/kde3
./configure --prefix=/opt/trinity
if KDE is installed in /opt/kde3. The downside is that you'll probably
if KDE is installed in /opt/trinity. The downside is that you'll probably
end up installing Kopete into directories used by your distribution,
instead of a separate path for your own packages like the /usr/local/
tree. Whether or not your package manager has problems with that and

Loading…
Cancel
Save