FS#42653 - [libreoffice-fresh] gconf support.
Attached to Project:
Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Saturday, 01 November 2014, 22:50 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 07 February 2015, 11:06 GMT
Opened by Hussam Al-Tayeb (hussam) - Saturday, 01 November 2014, 22:50 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 07 February 2015, 11:06 GMT
|
Details
Since gnome-desktop doesn't use gconf anymore, doesn't make
sense to drop the gconf support? (yes, I know it is optional
but it is linked against nevertheless)
It is not being used anyway. This can be done with --disable-lockdown --disable-gconf. I think lockdown support is still on gconf too so may as well disable it. |
This task depends upon
We are linking against a library that we don't use anymore.
In LibO git I couldn't get anything usefull from searching commit messages including "gconf" or "lockdown".
What LibO features read gconf keys? Do you have a full git checkout to grep?
I tend to drop gconf support using "--disable-lockdown".
Reading gconf settings seems to give only minor advantages for gnome users taking over a few settings (username, userpath, proxy settings).
Not sure what this lockdown is all about. I guess some network shared file locking. No idea why this is done in the app an not in the nfs/cfs (gvfs) client.
http://ftp.gnome.org/pub/gnome/sources/sabayon/ which appears to have not been ported to gnome3.
Also the settings (username, userpath, proxy settings) are in a gconf settings database which doesn't exist unless as remainder from an old gnome2 installation.