linux/poky.git/meta/recipes-gnome, branch uninative-1.9

librsvg: remove duplication in inherit

2018-04-05T13:49:08+00:00

Since gnomebase class already inherits autotools and pkgconfig, there is no need to repeat it here. (From OE-Core rev: bae5ced6eba78f1903e15d7f9dd7afc3c06e8955) Signed-off-by: Maxin B. John Signed-off-by: Richard Purdie

gcr: remove duplication in inherit

2018-04-05T13:49:07+00:00

Since gnomebase class already inherits autotools, there is no need to repeat it here. (From OE-Core rev: 9a514311fa062fa3f8bccc4c47e907f88221024a) Signed-off-by: Maxin B. John Signed-off-by: Richard Purdie

gtk-doc: don't regenerate gtk-doc in do_install

2018-03-25T08:40:42+00:00

In out-of-tree builds gtk-doc's setup-build target copies all the content from $srcdir to $builddir. However, if some of this content is regenerated at configure time this can happen: 1) configure writes new build/version.xml 2) make compile copies content, including the tarball's src/version.xml to build/version.xml, and generates gtk-doc. 3) make install notices build/version.xml is older than configure.status, so regenerates gtk-doc. gtk-doc generation is a slow process at the best of times, so doing it twice isn't good. (From OE-Core rev: 9ea9d61f26a942dbbc90070b40ba0209021a4b46) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gnome-desktop: do not assume time_t is long

2018-03-20T09:59:31+00:00

Replace use of atol() to set a time_t variable. (From OE-Core rev: 022866aa0ea6d7a8963d05bb10881e8d97bdf442) Signed-off-by: Joe Slater Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gtk-doc: refresh patches

2018-03-11T13:27:01+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 3277e60b6eefb3a1c858462bc89244f6577dca52) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gnome: refresh patches

2018-03-11T13:27:01+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 9c762156d5eab1582fdd1f5000e80a0a67d46152) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gtk+: refresh patches

2018-03-07T14:34:50+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 7ac8688c9fce49a005cbe9afe028453f6fea4e79) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gobject-introspection: refresh patches

2018-03-07T14:34:50+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 5a72d04296cc7aea5893cba29c6da1cf1469911b) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

epiphany: upgrade 3.26.5.1 -> 3.26.6

2018-03-04T11:35:41+00:00

(From OE-Core rev: 715a35eb4720ccab80c1c49f3f8d0e848917c8a2) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

librsvg: provide RECIPE_NO_UPDATE_REASON

2018-02-24T10:31:47+00:00

Rustification of librsvg from version 2.41.0 onwards creates the need for Rust compiler to build it. We need to push the upgrade of librsvg until we have Rust support in oe-core. (From OE-Core rev: 8eaa38ce7d16478710a73a72ef3dfdd2ba105d8e) Signed-off-by: Maxin B. John Signed-off-by: Ross Burton Signed-off-by: Richard Purdie