After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 664650 - gconf binaries not relocatable
gconf binaries not relocatable
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: gconf
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-23 15:43 UTC by Richard Purdie
Modified: 2011-11-28 14:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch allowing GCONF_BACKEND_DIR to be set from the environment (1.13 KB, patch)
2011-11-23 15:43 UTC, Richard Purdie 		none Details | Review

Description Richard Purdie 2011-11-23 15:43:05 UTC 
Created attachment 202006 [details] [review]
Patch allowing GCONF_BACKEND_DIR to be set from the environment

The path used for GCONF_BACKEND_DIR is hard coded into gconf at compile time. This makes it impossible to move the binary to a different location and run it which is a requirement within certain build environments where prebuilt binaries can be reused (for example Poky/OpenEmbedded).

If the directory could be overridden from the environment this restriction is removed and the binary can be relocated, see the attached patch for an example of this.
Comment 1 Rob Bradford 2011-11-28 13:51:00 UTC 
LGTM. Ross?
Comment 2 Ross Burton 2011-11-28 14:36:53 UTC 
Committed and pushed.  I use g_getenv because it does encoding magic which is probably useful in some edge cases.