On Tue, Apr 17, 2018 at 3:07 AM, Tanu Kaskinen <tanuk at iki.fi> wrote: > Originally the idea was to provide the "modules" schema with paprefs, > but since module-gsettings refers to the "modules" schema in its code, > that would make module-gsettings depend on paprefs, which is not good. > Now all schemas are provided by module-gsettings, so the paprefs > dependency is avoided. Unfortunately this means that if paprefs is > modified to load some new modules, the schema in pulseaudio needs to be > updated as well. I have two questions: 1. Wouldn't it be better to do the schema migration in pulseaudio then? I find it weird that the client is responsible for doing the migration instead if pulseaudio, if it is pulseaudio that ships the schema. 2. If the answer to (1) is "yes", maybe it would be best to have gsettings supersede gconf? Ie, offer the gconf module only when gsettings will not be built. I can't think of a usecase for having both enabled at the same time... -- Saludos, Felipe Sateler
