Re: [SyncEvolution] syncEvolution configuration structure and global properties
On Wed, 2011-06-29 at 09:22 -0700, Patrick Ohly wrote:
On Wed, 2011-06-29 at 18:06 +0200, Chris Kühl wrote:
> The "defaultPeer" value lives in default/peers/foo/config.ini, while
> I'd expect it to be in the .config/syncevolution directory because
> it's global.
Your expectation is correct. Jussi reported something similar recently:
https://bugs.meego.com/show_bug.cgi?id=19464
> This is triggered in the test TestMultipleConfigs.testSharing. Anyone
> see anything obvious?
I'll have a look.
I still can't reproduce it:
$ PATH=.:$PATH ~/src/syncevolution/test/test-dbus.py -v
TestMultipleConfigs.testSharing
set up configs and tests reading them ... ok
----------------------------------------------------------------------
Ran 1 test in 2.239s
OK
$ cat test-dbus/config/syncevolution/config.ini
# the peer which is used by default in some frontends, like the sync-UI
defaultPeer = foobar_peer
This is with SyncEvlution master commit 487c105a15, compiled with
--disable-shared --enable-static outside of the source directory.
I'll also try with --enable-shared, just in case.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.