linux/meta-openembedded.git/meta-oe/recipes-gnome, branch sumo

gtkmm3: add initial 3.22.2

2018-04-09T00:00:06+00:00

This is gtk3 version of gtkmm. There are no cnflicts with gtkmm for gtk2. Signed-off-by: Andreas Müller Signed-off-by: Armin Kuster

gtkmm: minor cleanup

2018-04-09T00:00:06+00:00

* it is enough to inherit gnomebase and distro_features_check * GNOME_COMPRESS_TYPE = "xz" is default for very long time Signed-off-by: Andreas Müller Signed-off-by: Armin Kuster

libunique: move to meta-xfce

2018-04-09T00:00:06+00:00

There are the only recipes using it still and I take the maintenace burden Signed-off-by: Andreas Müller Signed-off-by: Armin Kuster

libglade: remove

2018-03-29T23:48:43+00:00

* it failed in last world build * project is dead last release was in 2009 Signed-off-by: Andreas Müller

atkmm: only include when x11 in DISTRO_FEATURES

2018-03-12T16:59:32+00:00

Signed-off-by: Armin Kuster

gtk-doc: fix build failures for libgdata and libunique

2018-02-24T04:24:19+00:00

The failures appeared with recent gtk-doc 1.27 update in oe-core. Signed-off-by: Alexander Kanavin Signed-off-by: Armin Kuster

gnome-common: add PACKAGECONFIG for autoconf-archive

2017-12-11T15:54:12+00:00

Add PACKAGECONFIG for autoconf-archive. Default to enable it to avoid m4 file conflicts between gnome-common and autoconf-archive. e.g. IMAGE_INSTALL_append = " gnome-common autoconf-archive-dev" bitbake We enable autoconf-archive PACKAGECONFIG to avoid the following error. Error: Transaction check error: file /usr/share/aclocal/ax_check_enable_debug.m4 conflicts between attempted installs of gnome-common-3.18.0-r0.noarch and autoconf-archive-dev-2016.09.16-r0.core2_64 file /usr/share/aclocal/ax_code_coverage.m4 conflicts between attempted installs of gnome-common-3.18.0-r0.noarch and autoconf-archive-dev-2016.09.16-r0.core2_64 Signed-off-by: Chen Qi Signed-off-by: Armin Kuster

recipes: remove blacklisted recipes

2017-08-31T08:18:33+00:00

* as PNBLACKLIST message says, these recipes are blacklisted for long time and nobody showed any interest to fix them * remove all unused .patch and .inc files as well Signed-off-by: Martin Jansa

gnome-common: Add recipe (from oe-core)

2017-07-14T21:44:31+00:00

gnome-common is deprecated upstream (it's just a collection of m4 macros so that's not a huge issue) and more importantly is soon not used in oe-core. There are 6 recipes in meta-oe and 22 in meta-gnome that DEPEND on gnome-common: Move gnome-common unchanged to meta-oe. Signed-off-by: Jussi Kukkonen Signed-off-by: Martin Jansa

recipes: add removal date to PNBLACKLIST messages

2017-04-05T17:36:45+00:00

* based on discussion in pndeprecated thread: https://patchwork.openembedded.org/patch/137573/ update the messages to warn possible users that the recipe will be removed before the end of the next development cycle (before Yocto 2.4 is released). * updated with: sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs` * then noticed couple recipes being blacklisted only based on DISTRO_FEATURES, so removed those: meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb meta-oe/recipes-navigation/gypsy/gypsy.inc meta-oe/recipes-navigation/navit/navit.inc meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb * if it isn't fixed by this date, it's fair game to be removed whenever someone gets around to i Signed-off-by: Martin Jansa