summaryrefslogtreecommitdiff
path: root/README.multiarch
diff options
context:
space:
mode:
authorHelmut Grohne <helmut@subdivi.de>2016-06-10 07:26:12 +0200
committerHelmut Grohne <helmut@subdivi.de>2016-06-10 07:26:12 +0200
commite123f857a74e2ec8742ceebddebd7d296dcaca3c (patch)
treee597edbdbfac8eb88cb1ccaf5d5c9d80ada4bb0a /README.multiarch
parent1853954f5a600a51cea30cdab689d7774045fcb1 (diff)
downloaddebian-dedup-e123f857a74e2ec8742ceebddebd7d296dcaca3c.tar.gz
add a separate tool for generating hints on Multi-Arch headers
It builds on the core functionality of dedup, but uses a different database schema. Unlike dedup, it aborts downloading Arch:all packages early and consumes any other architecture in its entirety instead.
Diffstat (limited to 'README.multiarch')
-rw-r--r--README.multiarch14
1 files changed, 14 insertions, 0 deletions
diff --git a/README.multiarch b/README.multiarch
new file mode 100644
index 0000000..120f119
--- /dev/null
+++ b/README.multiarch
@@ -0,0 +1,14 @@
+There is a separate analysis application for detecting multiarch related bugs.
+It has the same requirements as the dedup application. It uses four files:
+
+ multiarchschema.sql
+ multiarchimport.py
+ multiarchanalyze.sql
+ multiarchanalyze.py
+
+With the schema you can initialize a database. The importer allows feeding the
+initial dataset or an updated dataset into the database by collecting data from
+a nearby Debian mirror. It is recommended to apply multiarchanalyze.sql once
+after the initial data import to avoid lots of changes on unused indices. The
+final step is generating the hints by running multiarchanalyze.py. Unless
+issuing ANALYZE, the analysis will be slow.