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?
Sounds like a good idea.
*** Bug 537654 has been marked as a duplicate of this bug. ***
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
agreed. Having it set in gnome2_environment_reset is likely the way to go.
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? :/
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.
[master b59e7c3] eclass/gnome2-utils.eclass: Ensure we don't rely on dconf/gconf while building, bug #511946 1 file changed, 3 insertions(+) Thanks :)
