Re: [PATCH] gtk+: don't provide gtk-update-icon-cache-native

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2013-03-27 at 10:23 +0000, Burton, Ross wrote:
> Hi Andreas,
> 
> On 27 March 2013 08:27, Andreas Müller <schnitzeltony@googlemail.com> wrote:
> > meta-browser: chromium
> 
> The latest commit to the Chromium 24 recipe changes gtk+-native to
> gtk+, so it appears that any gtk+-native references you're seeing are
> bad and the same fix should be applied to the other versions.
> 
> > openembedded-core: packagegroup-toolset-native
> 
> This is a packagegroup that builds ~all of the native packages.
> 
> > openembedded-core: sstate.bbclass
> 
>     def isPostInstDep(x):
>         if x in ["qemu-native", "gdk-pixbuf-native", "gtk+-native",
> "qemuwrapper-cross", "depmodwrapper-cross",
> "systemd-systemctl-native", "gtk-update-icon-cache-native"]:
>             return True
>         return False
> 
> Some sstate black magic.

That can just be removed if we don't use gtk+-native in any postinsts
which I don't believe we do now...

> > openembedded-core: seperatebuilddir.inc
> 
> Just a variable saying it can be built out of tree.

Right, that can also just be dropped.

> packagegroup-toolset-native is the only place that actually uses
> gtk+-native, so anyone actually using that for whatever purpose will
> need to set the preferred provider.

This can also just get dropped, it was only there to allow building the
collection of native recipes.

So as far as I'm concerned all these references can just be removed.

Cheers,

Richard