hey IsoLinearCHiP,
In fact, if you set a non existing conffile to gconf, this one will just check
if it exists and ignore it if not. This is done only one on the server side and
so, it's a fast operation.
In addition, it's better to do that at that stage for bootime speed (as
the check will be done later, the first time gconf is invoked and not at
each time you log in, and every other processes waiting on the check to
appear). Also, you probably already know that gconf is going away quite
soon, so I think this is not something we should really work on.
So, in a summary, technically this is a good idea, but in practice, I
think we unfortunately shouldn't change that, for speed and
effectiveness issue.
Thanks a lot for working on that though and do not hesitate to submit
other ideas to ubuntu! :)
** Changed in: gconf (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/914102
Title:
Suggestion: do not set gconf env vars to non-existing files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/914102/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
