| Summary: | gconf useflag should be added to make.defaults for the gnome subprofile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Fab <netbox253> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Fab
2010-08-22 09:54:38 UTC
What problem did you have with ekiga compiled with "gnome" and "-gconf" USE flags? (In reply to comment #1) > What problem did you have with ekiga compiled with "gnome" and "-gconf" USE > flags? > Not really a problem. I actually had to modify the default ports of ekiga to try to solve a problem. The documentation that I was reading talked about gconf keys to modify, but I could not find them. I then realized that ekiga was built with "-gconf", and all configuration stuff was in a plain text file. But since I'm using the gnome subprofile, I was expecting that I had the gconf support auto-enabled. The problem here is that "gconf" support is being deprecated (as you probably know, future Gnome 3 won't even use it), looking at ebuilds still using gconf USE flags, looks like in most of them it's not really a requirement for working under Gnome (looks more like "optional"), and, for example, with compiz, it looks to be recommended to disable that support if possible. Then, if ekiga-3 really needs to have gconf enabled on a Gnome based system, maybe we could enable it only for that ebuild. (In reply to comment #3) > The problem here is that "gconf" support is being deprecated (as you probably > know, future Gnome 3 won't even use it) I didn't know that. > Then, if ekiga-3 really needs to have gconf enabled on a Gnome based system, > maybe we could enable it only for that ebuild. > No, it doesn't really need it, I guess that it works without it, but when you read the ekiga wiki [1] for troubleshooting, tips and tricks, they speak almost everywhere about gconf, gconf-editor and gconftool-2. If gconf will disappear in a near future, it doesn't worth to activate it, but in the other hand, applications that currently use gconf will probably migrate to the new GSettings/dconf system ? It is not really important, but I was simply surprised to not have the gconf support enabled with the gnome profile. [1] http://wiki.ekiga.org/index.php/Main_Page Closing per last comments. gconf replacement is achieved by migrating to gsettings, you can still use gconf as a backend for gsettings, but dconf or nothing at all if you wish so. Applications will not link against gconf anymore but against gsettings which is in glib, so always present for a glib based application. No more use flag, no more problem :). |
