app-editors/gedit/gedit-3.8.3.ebuild: RDEPEND: ~amd64-fbsd(default/bsd/fbsd/amd64/9.1) ['gnome-base/dconf'] app-editors/gedit/gedit-3.10.3.ebuild: RDEPEND: ~amd64-fbsd(default/bsd/fbsd/amd64/9.1) ['gnome-base/dconf'] We need dconf keyworded here for gedit Thanks
ping
@amd64-fbsd, this is a bit urgent to us because most apps need dconf with current glib versions to really work instead of relying on the longly deprecated gconf
Looks like hppa also missed dconf keyword
What does HPPA need dconf for?
well, most glib consumers that were using gconf will be moved to dconf (if not already). Some are using gconf as fallback but that is not desired at all (gconf is dead for ages, with known bugs and nobody cares about it)
To be more precise, glib can use various backends for storing gsettings, memory, gconf or dconf. * dconf is the upstream recommended backend. * gconf works as a backend but not sure it is really supported. * memory, well, you just loose settings from one run of your application to another. Due to various applications simply crashing in the absence of a backend and us simply wanting the best default experience (of saving your settings) out of the box, we would like to add dconf to glib dependencies hence need some keywording work. It is a small and quick to compile package so we don't plan on making it optional and are open to making it a || later if new backends appear.
Marked ~hppa. USE=dconf isn't masked for HPPA, so I guess that should help in the future?
I guess the remaining arch team is ok with dropping it
