Bug 511946

Summary:	gnome2.eclass: export GSETTINGS_BACKEND="memory"
Product:	Gentoo Linux	Reporter:	Pacho Ramos <pacho>
Component:	[OLD] GNOME	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED FIXED
Severity:	normal	CC:	esigra
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	262490

Description Pacho Ramos gentoo-dev

2014-05-31 10:41:29 UTC

I have seen many packages with failing tests due dconf stuff being needed (but not yet installed). Usually this can be avoided by using memory. I have a doubt: should we export it in general for all build process or only for tests?

Comment 1 Gilles Dartiguelongue (RETIRED) gentoo-dev

2014-12-26 23:04:34 UTC

Sounds like a good idea.

Comment 2 Pacho Ramos gentoo-dev

2015-04-18 12:52:09 UTC

*** Bug 537654 has been marked as a duplicate of this bug. ***

Comment 3 Pacho Ramos gentoo-dev

2015-12-03 16:10:05 UTC

It should probably be done for the full build as it shouldn't try to touch or rely on the dconf stuff from real system at any time I guess

Comment 4 Gilles Dartiguelongue (RETIRED) gentoo-dev

2015-12-06 22:36:12 UTC

agreed. Having it set in gnome2_environment_reset is likely the way to go.

Comment 5 Pacho Ramos gentoo-dev

2015-12-12 09:36:20 UTC

Nice, should we do it only for eapi6 and newer to be more "safe" or we could take the risk of setting it for all eapis and expecting it doesn't cause any kind of issue? :/

Comment 6 Gilles Dartiguelongue (RETIRED) gentoo-dev

2015-12-13 12:02:22 UTC

It should not break anything as this is the default backend if dconf/gconf is not installed and if dconf/gconf is used it caused sandbox errors iirc.

Comment 7 Pacho Ramos gentoo-dev

2015-12-14 21:00:48 UTC

[master b59e7c3] eclass/gnome2-utils.eclass: Ensure we don't rely on dconf/gconf while building, bug #511946
 1 file changed, 3 insertions(+)

Thanks :)