Re: [Tracker] Removing Maemo support upstream

[Carlos Garnacho <carlosg gnome org>]

Hi!,

On Tue, May 23, 2017 at 12:30 PM, Sam Thursfield <ssssam gmail com> wrote:
> 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

Let's keep these, they might be used elsewhere.

>   * 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

But I'll be delighted to see all this go :). it's worth pointing out
that --enable-maemo seems just used in order to install the 91-maemo
ontology, but the miner-apps stuff is under a HAVE_MEEGOTOUCH, so it
is possible to have a miner-apps using an ontology that is not
installed. This, and code that we can't possibly test (eg. the stuff
under HAVE_MEEGOTOUCH defines) makes us look bad IMO :(.

> 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?

I think most stuff can be just implemented using tracker libraries and
maintained standalone, no need to patch tracker.

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

Did we get enough silence already? :p

Cheers,
  Carlos