Re: [mer-general] dconf will land near you
dconf has been puhed already. The build however is broken since it seems that it's not hooked and I don't know how to hook it. I guess someone needs to check the build itself? Cheers, On Tue, May 06, 2014 at 02:18:31PM +0300, Mohammed Sameer wrote: > On Mon, May 05, 2014 at 02:50:13PM +0300, Mohammed Sameer wrote: > [...] > > I will be merging the dconf patches for mlite > > https://github.com/nemomobile/mlite/ fairly soon. > > fairly soon = I am aiming for tomorrow. > > I will not merge stuff today since I feel I still need to give more info and > time. > I will be aiming for tomorrow morning. > > This PR will have to be merged: > https://github.com/nemomobile-packages/gst-plugins-good/pull/3 > It drops the gconf elements from gstreamer. > > This is another one for nemo-theme-default: > https://github.com/nemomobile/nemo-theme-default/pull/8 > There you can see how the nemo database is being populated. > > I have also pushed the migration tool to the dconf repos: > https://github.com/mer-packages/dconf/blob/master/gconf2dconf.cpp > > Some more work is needed for the tool so it'd be fired during boot and does > the conversion > only once. I will be working on that tomorrow. > > > The PR are https://github.com/nemomobile/mlite/pull/13 and > > https://github.com/nemomobile/mlite/pull/12 > Those I announced yesterday already ;-) > > > What is unknown to me is if the ohm gconf plugin is being used by nemo or > > not. > > If it's used then we need to find a way to fix it and/or replace it (Which > > will delay > > the dconf land but that's fine) or we simply remove it if we don't use it. > > I'd still appreciate feedback on that part as I don't know. > > Cheers, > > -- > GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F 280E CB66 8E29 A3FD 0DF7 > Debian User and Developer. > Homepage: www.foolab.org -- GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F 280E CB66 8E29 A3FD 0DF7 Debian User and Developer. Homepage: www.foolab.org
Re: [mer-general] dconf will land near you
On Mon, May 05, 2014 at 02:50:13PM +0300, Mohammed Sameer wrote: [...] > I will be merging the dconf patches for mlite > https://github.com/nemomobile/mlite/ fairly soon. > fairly soon = I am aiming for tomorrow. I will not merge stuff today since I feel I still need to give more info and time. I will be aiming for tomorrow morning. This PR will have to be merged: https://github.com/nemomobile-packages/gst-plugins-good/pull/3 It drops the gconf elements from gstreamer. This is another one for nemo-theme-default: https://github.com/nemomobile/nemo-theme-default/pull/8 There you can see how the nemo database is being populated. I have also pushed the migration tool to the dconf repos: https://github.com/mer-packages/dconf/blob/master/gconf2dconf.cpp Some more work is needed for the tool so it'd be fired during boot and does the conversion only once. I will be working on that tomorrow. > The PR are https://github.com/nemomobile/mlite/pull/13 and > https://github.com/nemomobile/mlite/pull/12 Those I announced yesterday already ;-) > What is unknown to me is if the ohm gconf plugin is being used by nemo or not. > If it's used then we need to find a way to fix it and/or replace it (Which > will delay > the dconf land but that's fine) or we simply remove it if we don't use it. I'd still appreciate feedback on that part as I don't know. Cheers, -- GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F 280E CB66 8E29 A3FD 0DF7 Debian User and Developer. Homepage: www.foolab.org signature.asc Description: Digital signature
[mer-general] dconf will land near you
Hi, dconf is a change that has been planned for a long time. I will be merging the dconf patches for mlite https://github.com/nemomobile/mlite/ fairly soon. fairly soon = I am aiming for tomorrow. The PR are https://github.com/nemomobile/mlite/pull/13 and https://github.com/nemomobile/mlite/pull/12 What this does is it switches mlite to dconf and dconf will be the storage backend used. There is a tool that will migrate the settings for the user from gconf to dconf upon the next boot. I am still putting the final touches for the migration itself but I hope to push it out today. dconf will be shipped with 2 read only system databases for storing default configuration: - nemo which will contain the defaults for nemomobile - vendor which is intended for vendors to override the nemo ones And then the normal read and write database for storing user specific configuration. What is unknown to me is if the ohm gconf plugin is being used by nemo or not. If it's used then we need to find a way to fix it and/or replace it (Which will delay the dconf land but that's fine) or we simply remove it if we don't use it. I will also be documenting the 2/3 databases used above and how to add defaults for the system and apps in a README. Is the above plan fine for everybody? Does anyone know if the gconf ohm plugin is being used ? Cheers, -- GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F 280E CB66 8E29 A3FD 0DF7 Debian User and Developer. Homepage: www.foolab.org
