summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEnrico Zini <enrico@enricozini.org>2015-06-18 10:30:42 +0200
committerEnrico Zini <enrico@enricozini.org>2015-06-18 10:32:23 +0200
commitee843d09ffa03ec31a47d14e5bc044ac30e07720 (patch)
tree1750835dc407eb3bee835598e813eb50af07a5fc /doc
parent31e61801f7b29984777cc7d8260e2378a36e0f4e (diff)
downloadlibept-ee843d09ffa03ec31a47d14e5bc044ac30e07720.tar.gz
Remove ept-cache
Diffstat (limited to 'doc')
-rw-r--r--doc/FAQ25
1 files changed, 0 insertions, 25 deletions
diff --git a/doc/FAQ b/doc/FAQ
deleted file mode 100644
index 9c36897..0000000
--- a/doc/FAQ
+++ /dev/null
@@ -1,25 +0,0 @@
-Frequently Asked Questions for ept-cache
-========================================
-
-Q: How does ept-cache related work?
-A: The 'related' function of ept-cache relies on the Xapian index and works
- like this:
- 1. Look up the Xapian records for all the package names given in the
- command line;
- 2. Fetch all the tokens indexed for all the packages given, and build an OR
- query with all those tokens;
- 3. Output the results of the query.
-
-Q: How come the results of ept-cache seem to be in random order?
-A: By default, ept-cache gives results in decreasing order of relevance.
- Simply put, it gives the best results first.
-
- ept-cache, however, allows query results to degenerate into less and less
- approximate matches, and sometimes this leads to a point where results start
- to look random.
-
- If you want to have an idea of what is going on, use the --debug option to
- see how the quality cutoff point is computed, then the --full option to
- see the Search-Score: values. You can also use --cutoff to set a higher
- quality cutoff value (default is to show results that are at least 50% as
- good as the top result).