On Wed, Sep 6, 2017 at 9:23 PM, Mark Hatle <[email protected]> wrote: > This resolves a failure of the yocto-compat-layer.py script. Changing the > PACKAGECONFIG setting by just including a layer can cause problems. > > Signed-off-by: Mark Hatle <[email protected]> > --- > meta-gnome/conf/enable_gnome.conf | 2 ++ > meta-gnome/recipes-devtools/glade/glade3_%.bbappend | 1 - > 2 files changed, 2 insertions(+), 1 deletion(-) > delete mode 100644 meta-gnome/recipes-devtools/glade/glade3_%.bbappend > > diff --git a/meta-gnome/conf/enable_gnome.conf > b/meta-gnome/conf/enable_gnome.conf > index 883a6f5..7e711ee 100644 > --- a/meta-gnome/conf/enable_gnome.conf > +++ b/meta-gnome/conf/enable_gnome.conf > @@ -1 +1,3 @@ > AVAHI_GTK_pn-avahi-ui = "gtk gtk3" > + > +PACKAGECONFIG_pn-glade3 = "gnome" > diff --git a/meta-gnome/recipes-devtools/glade/glade3_%.bbappend > b/meta-gnome/recipes-devtools/glade/glade3_%.bbappend > deleted file mode 100644 > index 3abacfb..0000000 > --- a/meta-gnome/recipes-devtools/glade/glade3_%.bbappend > +++ /dev/null > @@ -1 +0,0 @@ > -PACKAGECONFIG ??= "gnome" > -- > 1.8.3.1 > Yet another stupid question (yes I need gnome support for working with glade3): How is enable_gnome.conf supposed to be activated?
For the record: This is yet another patch kicking things off for the sake of yocto-compat-layer script. Is meta-gnome supposed to be yocto compatible? Was this decided by 'community'? But I am sure I missed another point... Andreas -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
