Re: git: d631449922df - main - compiz: disable gconf support

On 2022-06-09 06:20, Tomoaki AOKI wrote:
> On Thu, 9 Jun 2022 09:07:25 +0200
> Baptiste Daroussin <bapt@freebsd.org> wrote:
> 
>> On Wed, Jun 08, 2022 at 10:28:36PM -0700, Chris wrote:
>> > On 2022-06-08 18:47, Tomoaki AOKI wrote:
>> > > Hi.
>> > >
>> > > How can I convert settings stored in gconf backend?
>> > >
>> > > Maybe needs migrating to ~/.config/compiz/compizconfig/Default.ini,
>> > > for each user, but not sure how to do so.
>> > > The mapping of each entry on Default.ini are unclear.
>> > I approved the proposal as Gconf will no longer be available. I'm
>> > going to take a look at this to see what's possible. Then implement/document
>> > it. In the meantime you should be able to lock your current version of
>> > compiz*
>> > to maintain it's current functionality.
>> > If you (or anybody else) finds a good solution/alternative before I
>> > do. Please open a pr(1).
>> >
>> > Chris
>> 
>> So be honnest I have no idea how to convert from gconf to anything else.
>> I have been working on decommisionning gconf and ended up on the compiz 
>> port,
>> which is why I did contact the maintainer.
>> 
>> Generally the way to migrate out of gconf is to to move to gsettings which 
>> is
>> the gconf replacement (part of glib) and there is a tool that exist for 
>> that:
>> gsettings-data-convert(1) provided by the latest version of gconf, which 
>> should
>> do the trick. (note that apparently compiz do support gsettings if I trust
>> https://wiki.archlinux.org/title/Compiz (don't know if it needs a tweak in 
>> the
>> ports or not.
>> 
>> Another way: as far as I know gconf is using xml so it might be possible to 
>> write
>> an xslt which converts from this xml to a .ini, but not sure how trivial 
>> this is.
>> 
>> Best regards,
>> Bapt
> 
> Unfortunately, `gsettings-data-convert --dry-run --verbose` shows
> nothing related with compiz.
> 
>   ===== Quot =====
> 
> File 'org.gnome.crypto.pgp.convert already converted, skipping
> File 'brasero.convert already converted, skipping
> File 'gvfs-smb.convert already converted, skipping
> File 'gsettings-desktop-schemas.convert already converted, skipping
> Collecting settings for schema 'org.gnome.sound-juicer'
> Skipping GConf key '/apps/sound-juicer/audio_profile', no user value
> Skipping GConf key '/apps/sound-juicer/base_uri', no user value
> Skipping GConf key '/apps/sound-juicer/eject', no user value
> Skipping GConf key '/apps/sound-juicer/file_pattern', no user value
> Skipping GConf key '/apps/sound-juicer/open_completed', no user value
> Skipping GConf key '/apps/sound-juicer/path_pattern', no user value
> Skipping GConf key '/apps/sound-juicer/strip-special', no user value
> Set key 'volume' to double '1'
> File 'gvfs-dns-sd.convert already converted, skipping
> File 'org.gnome.crypto.pgp_keyservers.convert already converted,
> skipping File 'totem.convert already converted, skipping
> File 'wm-schemas.convert already converted, skipping
> File 'gnome-settings-daemon.convert already converted, skipping
> File 'opensubtitles.convert already converted, skipping
> Collecting settings for schema 'org.gnome.totem.plugins.pythonconsole'
> Skipping GConf key '/apps/totem/plugins/pythonconsole/rpdb2_password',
> no user value Directory '/usr/share/GConf/gsettings' does not exist,
> nothing to do
> 
>   ===== End quot =====
> 
> Possibly, gsettings-data-convert shows nothing for sucessful job,
> though.
> 
> Not done actual run as I'm not enough sure.
> 
> 
> Another info is that I could export gconf settings as XML data by
> `gconftool-2 --recursive-list /schemas/apps/compiz` for schemas and by
> `gconftool-2 --recursive-list /apps/compiz` for actual settings.
> 
> It would be better waiting for Chris's work.
gsettings(1) is your friend -- man 1 gsettings
Try: gsettings list-recursively as an example.
My current thoughts on the best path forward is dconf(1). IOW
those currently using Gconf can convert their settings to dconf and
they're effectively done. Those not already using Gconf will be unaware/
unaffected. They'll just use dconf(1). BUT, and this is important, I
haven't yet setup a testbed to discover whether Compiz will accept the
dconf backend under [gnome-session] in Compiz config. So at this point
the Compiz part is hypothetical. However, there is no real downside to
converting Gconf to Dconf in either case.

Just thought I'd mention it.

Chris
> 
> Thanks in advance!
> 
> P.S.
> gsettings-data-convert looks for /usr/share/GConf/gsettings, but
> it should be ${LOCALBASE}/share/GConf/gsettings on FreeBSD.
> But there are no data related to compiz there.