[tracker-miners/wip/carlosg/tracker-3.0-api-breaks] docs: Remove references to TRACKER_SPARQL_BACKEND



commit f350518627df0bd29fa41ac379a255fa2bfe319f
Author: Sam Thursfield <sam afuera me uk>
Date:   Fri Jan 17 00:27:11 2020 +0100

    docs: Remove references to TRACKER_SPARQL_BACKEND

 docs/manpages/tracker-search.1 | 19 -------------------
 docs/manpages/tracker-tag.1    | 19 -------------------
 2 files changed, 38 deletions(-)
---
diff --git a/docs/manpages/tracker-search.1 b/docs/manpages/tracker-search.1
index 06762f5af..3e18867fe 100644
--- a/docs/manpages/tracker-search.1
+++ b/docs/manpages/tracker-search.1
@@ -110,25 +110,6 @@ yield better results if the FTS ranking is off.
 This disables any ANSI color use on the command line. By default this
 is enabled to make it easier to see results.
 
-.SH ENVIRONMENT
-.TP
-.B TRACKER_SPARQL_BACKEND
-This option allows you to choose which backend you use for connecting
-to the database. This choice can limit your functionality. There are
-three settings.
-
-With "\fBdirect\fR" the connection to the database is made directly to
-the file itself on the disk, there is no intermediary daemon or
-process. The "\fBdirect\fR" approach is purely \fIread-only\fR.
-
-With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
-the database queuing all requests and managing the connections via an
-IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
-approach you can use if you want to \fIwrite\fR to the database.
-
-With "\fBauto\fR" the backend is decided for you, much like it would
-be if this environment variable was undefined.
-
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-stats (1),
diff --git a/docs/manpages/tracker-tag.1 b/docs/manpages/tracker-tag.1
index c4e3285e5..8fd773886 100644
--- a/docs/manpages/tracker-tag.1
+++ b/docs/manpages/tracker-tag.1
@@ -78,25 +78,6 @@ $ tracker-tag -s -t sliff sloff
 Should show files in the database that have both the \fIsliff\fR and
 \fIsloff\fR tags.
 
-.SH ENVIRONMENT
-.TP
-.B TRACKER_SPARQL_BACKEND
-This option allows you to choose which backend you use for connecting
-to the database. This choice can limit your functionality. There are
-three settings.
-
-With "\fBdirect\fR" the connection to the database is made directly to
-the file itself on the disk, there is no intermediary daemon or
-process. The "\fBdirect\fR" approach is purely \fIread-only\fR.
-
-With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
-the database queuing all requests and managing the connections via an
-IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
-approach you can use if you want to \fIwrite\fR to the database.
-
-With "\fBauto\fR" the backend is decided for you, much like it would
-be if this environment variable was undefined.
-
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-sparql (1),


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]