--- Comment #12 from qkmiao <qiankun.miao(a)intel.com> 2010-09-16 00:07:23 PDT ---
Updated dbus-testing branch.
(In reply to comment #7)
I disagree. I want the testing to cover the bits and bytes that we
something else, *in particular* if it gets compiled with different configure
options. Different options always come with the risk of hiding bugs that occur
with the ones used for release.
We don't need to get source code and compile it for dbus-testing, just use the
same as client-testing. Right? By now, dbus-testing and client-testing scripts
have some differences in build path, install path, result path. Do we need to
align dbus-testing with client-testing?
Another approach is that we can build client-testing and dbus-testing
separately with the same configure options.
Regarding the keyring, how about this: make the usage of the keyring
configurable via ~/.config/syncevolution/config.ini (similar to the "current
config" setting), turn the "--keyring" parameter into an alias for this
property (similar to "--sync"). Then turn off the keyring in the chroot.
A new property "GnomeKeyring" has been added to enable or disable gnomekeyring
at runtime. Help to review code in dbus-testing branch.
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.