http://bugs.meego.com/show_bug.cgi?id=5609
--- Comment #7 from pohly <[email protected]> 2010-09-09 04:24:20 PDT --- (In reply to comment #6) > > Sorry, I don't understand how this is meant to work. What I expect to > > happen is > > this: > > - runtest.py is used to compile binaries > > - if the binaries were compiled successfully, > I think it's not so needed since they use different configure options. To > simple, I like to leave it as current status. I disagree. I want the testing to cover the bits and bytes that we ship, not 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. > > also run test-dbus.py using them and send out the results > dbus-server uses gnome-keyring. dbus daemon pops up a dialog to input password > to access keyring in usual. We don't find a good method to solve it in chroot > environment. I suggest just testing it in current environment. What do you mean? Don't test as part of the nightly testing? 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. -- 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. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
