[Tracker] Removing Maemo support upstream

[Sam Thursfield <ssssam gmail com>]

Hi all
There's a bunch of references to Maemo in the Tracker source code.
Specifically we have:

  * the 91-maemo ontology -- only referenced in some special casing in
the applications miner
  * the 39-mto (Maemo transfer ontology) -- unused in core Tracker code
  * the 40-mlo (Maemo location ontology) -- unused in core Tracker code
  * the 41-mfo (Maemo feeds ontology)  -- unused in core Tracker code
  * the 92-slo (Simplified Maemo location ontology) -- still widely used
  * the --enable-maemo config flag
  * the create-tests-xml.py and create-tests-aegis.py scripts in
tests/functional-tests
  * some Maemo-specific functional tests
  * some special casing in the applications miner
  * the Maemo userguides miner

The Maemo-specific bits of the functional tests are getting in my way
quite a bit, I don't have any way of testing out that the
scratchbox-based code paths actually work so I don't think we should
be carrying them upstream.

The ontologies and the user-guides miner don't cause me many issues,
but it might make sense to remove these as well since we're not using
them in the core of Tracker at all.

The last release of Maemo or Meego appears to be 5 years ago and I
don't know that more are planned.

Mer / Sailfish OS still uses Tracker and have a fork at
<https://git.merproject.org/mer-core/tracker/>. They're building with
--enable-maemo plus an additional --enable-nemo flag.

I've CC'ed Andrew who seems to maintain that -- would you be happy to
carry the Maemo specific bits that you're using as downstream patches
from now on?

Is anyone else using these ontologies and code paths that I wasn't aware of?

Thanks
Sam