mime apps specification

[David Faure]

Hi Ryan,
(sorry for the delay, I was travelling)

On Wednesday 09 April 2014 13:20:01 you wrote:
> hi,
> 
> On Wed, Apr 9, 2014, at 11:31, David Faure wrote:
> > Yes. But don't forget that there are mimeapps.list at other levels
> > (XDG_CONFIG_*), where there are no desktop files at all.
> > 
> > And therefore no cache there, but the point is that the algorithms in our
> > libs
> > have to take this into account as well. For instance we can't say that a
> > mimeapps.list can only refer to .desktop files of that current level and
> > below, since at the /etc level that would mean: none.
> 
> I think we crossed meanings somewhere along the way.  From my view,
> *all* of the desktop files are "below" ~/.config and /etc, because they
> are in directories that come later in the list (in precedence order).

You are right, I remembered wrong the ordering from the spec.

OK, the main point remains though: we need our library code to be able to 
handle mimeapps.list files that are not in a binary cache -- it in fact sits 
on top of the binary cache.

So my proposal is to extend that to the mimeapps.list files that live within 
the data dirs, i.e. where the binary caches are. If we follow your suggestion 
to even deprecate added/removed in data dirs, then we can expect that this 
will not hurt performance, compared to integrating the added/removed into the 
binary caches.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5