[oe-commits] [openembedded-core] 53/56: gobject-introspection.bbclass: Disable writing to $HOME/.cache/g-ir-scanner

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a commit to branch master-next
in repository openembedded-core.

commit 5e5af682ab0faa9c598b73c6d0e981a6a5980b21
Author: Jason Wessel <jason.wessel at windriver.com>
AuthorDate: Wed Apr 10 17:54:02 2019 -0400

    gobject-introspection.bbclass: Disable writing to $HOME/.cache/g-ir-scanner
    
    Investigation of an end user going over their quota in the user's home
    directory showed that the gobject-instrospection is writing files into
    the ~/.cache/g-ir-scanner when building -native packages.  The test
    package in this case was gdk-pixbuf-native.
    
    Setting the GI_SCANNER_DISABLE_CACHE in the bbclass should be all that
    is needed.  The qemu wrapper was already setting this properly, but we
    also need it for the -native builds.
    
    meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:131:
    export GI_SCANNER_DISABLE_CACHE=1
    
    Signed-off-by: Jason Wessel <jason.wessel at windriver.com>
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 meta/classes/gobject-introspection.bbclass | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/classes/gobject-introspection.bbclass b/meta/classes/gobject-introspection.bbclass
index 504f75e..9e41849 100644
--- a/meta/classes/gobject-introspection.bbclass
+++ b/meta/classes/gobject-introspection.bbclass
@@ -37,6 +37,9 @@ DEPENDS_append_class-nativesdk = " gobject-introspection-native"
 # This is used by introspection tools to find .gir includes
 export XDG_DATA_DIRS = "${STAGING_DATADIR}:${STAGING_LIBDIR}"
 
+# Disable writing to $HOME/.cache/g-ir-scanner
+export GI_SCANNER_DISABLE_CACHE = "1"
+
 do_configure_prepend_class-target () {
     # introspection.m4 pre-packaged with upstream tarballs does not yet
     # have our fixes

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.