[tracker/wip/carlosg/tracker-3.0-api-breaks: 65/100] Remove references to obsolete environment variables

[Carlos Garnacho <carlosg src gnome org>]

commit 4a165fda09040275413d49c5f6a54b7fcc6487b4
Author: Sam Thursfield <sam afuera me uk>
Date:   Fri Jan 17 00:26:12 2020 +0100

    Remove references to obsolete environment variables
    
    TRACKER_SPARQL_BACKEND is no more. Neither TRACKER_SPARQL_CACHE_SIZE.

 docs/manpages/tracker-info.1                  | 19 ---------------
 docs/manpages/tracker-sparql.1                | 19 ---------------
 docs/reference/libtracker-sparql/overview.xml | 35 ---------------------------
 tests/libtracker-sparql/tracker-fd-test.c     |  2 --
 4 files changed, 75 deletions(-)
---
diff --git a/docs/manpages/tracker-info.1 b/docs/manpages/tracker-info.1
index fbbc68fac..eb2925e3b 100644
--- a/docs/manpages/tracker-info.1
+++ b/docs/manpages/tracker-info.1
@@ -53,25 +53,6 @@ for subjects, predicates and objects; otherwise, shortened URIs are
 used, and all the prefixes Tracker knows about are printed at the top
 of the output.
 
-.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).
diff --git a/docs/manpages/tracker-sparql.1 b/docs/manpages/tracker-sparql.1
index 78ea98971..c34b89827 100644
--- a/docs/manpages/tracker-sparql.1
+++ b/docs/manpages/tracker-sparql.1
@@ -217,25 +217,6 @@ $ tracker sparql --get-longhand nmm:MusicPiece
 http://www.tracker-project.org/temp/nmm#MusicPiece
 .fi
 
-.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 EXAMPLES
 .TP
 List all classes
diff --git a/docs/reference/libtracker-sparql/overview.xml b/docs/reference/libtracker-sparql/overview.xml
index 4eb398160..81b1729da 100644
--- a/docs/reference/libtracker-sparql/overview.xml
+++ b/docs/reference/libtracker-sparql/overview.xml
@@ -87,41 +87,6 @@ $ pkg-config --libs tracker-sparql-0.12
            $HOME/.config/tracker/
          </para>
        </listitem>
-       <listitem>
-         <emphasis>TRACKER_SPARQL_BACKEND</emphasis>
-         <para>
-           Backends for libtracker-sparql are dynamically loaded at
-           run time. Currently there are only two backends which are
-           <link linkend="overview-tracker-connection-methods">explained
-           more closely</link> in the previous chapter. In short,
-           this environment variable gives the client the ability to
-           directly mandate which backend they want to use. The
-           value can be set to either "direct" or "bus". A "direct"
-           value means the direct access approach will be forced. A
-           "bus" value means a D-Bus / IPC approach will be forced.
-         </para>
-       </listitem>
-       <listitem>
-         <emphasis>TRACKER_SPARQL_CACHE_SIZE</emphasis>
-         <para>
-           Tracker caches database statements which occur frequently to make
-           subsequent repeat queries much faster. The cache size is
-           set to <emphasis>100</emphasis> by default for each type
-           (select and update queries). This must be at
-           least <emphasis>2</emphasis> as a minimum, any less and a
-           value of <emphasis>3</emphasis> is used instead. The
-           number represents the number of cached statements to keep
-           around. This environment variable is used mainly for
-           testing purposes.
-         </para>
-         <para>
-           Tracker's store also has environment variables to control
-           this behavior, see the manual pages
-           for <emphasis>tracker-store</emphasis>
-           regarding <emphasis>TRACKER_STORE_SELECT_CACHE_SIZE</emphasis>
-           and <emphasis>TRACKER_STORE_UPDATE_CACHE_SIZE</emphasis>.
-         </para>
-       </listitem>
        <listitem>
          <emphasis>TRACKER_VERBOSITY</emphasis>
          <para>
diff --git a/tests/libtracker-sparql/tracker-fd-test.c b/tests/libtracker-sparql/tracker-fd-test.c
index fd96037c4..add222e81 100644
--- a/tests/libtracker-sparql/tracker-fd-test.c
+++ b/tests/libtracker-sparql/tracker-fd-test.c
@@ -783,8 +783,6 @@ main (gint argc, gchar **argv)
                g_log_set_handler ("Tracker", G_LOG_LEVEL_DEBUG | G_LOG_LEVEL_INFO, g_log_default_handler, 
NULL);
        }
 
-       /* test D-Bus backend */
-       g_setenv ("TRACKER_SPARQL_BACKEND", "bus", TRUE);
        g_setenv ("TRACKER_TEST_DOMAIN_ONTOLOGY_RULE", TEST_DOMAIN_ONTOLOGY_RULE, TRUE);
        g_setenv ("TRACKER_DB_ONTOLOGIES_DIR", TEST_ONTOLOGIES_DIR, TRUE);