summaryrefslogtreecommitdiffstats
path: root/Documentation/ConduitProgrammingTutorial/index.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/ConduitProgrammingTutorial/index.tex')
-rw-r--r--Documentation/ConduitProgrammingTutorial/index.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/ConduitProgrammingTutorial/index.tex b/Documentation/ConduitProgrammingTutorial/index.tex
index aed082e..66b17f3 100644
--- a/Documentation/ConduitProgrammingTutorial/index.tex
+++ b/Documentation/ConduitProgrammingTutorial/index.tex
@@ -147,7 +147,7 @@ From your system's point of view, a conduit is a shared library which is loaded
on demand by KPilot. This means that as long as you don't do a sync, the conduit will not
be in memory. Once a hotsync is initiated, kpilotDaemon (the process running in
the background that does the actual sync) loads the conduit, let's say its name
-is "malconduit" and it is installed as /opt/kde3/lib/kde3/libmalconduit.so. It
+is "malconduit" and it is installed as /opt/trinity/lib/trinity/libmalconduit.so. It
then calls the function \code{init\_libmalconduit} (the name after init\_ is the
filename of the library), which needs to return a pointer to an instance
of a \class{KLibFactory} subclass.