gdm dconf changes


GDM 3.2.0 uses dconf in a sort of weird way involving generating
binary dconf databases at build/install time in dummy dbus sessions.

I tried to improve that in GDM 3.2.1 by generating text keyfiles instead:

This second try was still a bit contrived and complicated for
distributors, so Vincent filed a bug:

I've now done a GDM release that dramatically simplifies how
GDM does settings:

With this change, though, distributors do need to remember to run
"dconf update" as part of their packaging post transaction hooks.

Just a heads up,

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]