http://bugs.meego.com/show_bug.cgi?id=1357 Summary: syncevolution --version: information about backends? Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: Netbook OS/Version: IA Status: ASSIGNED Severity: normal Priority: Low Component: SyncEvolution AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: jingke.zhang(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-default-bugs(a)meego.bugs Estimated Hours: 0.0 This is from http://bugzilla.moblin.org/show_bug.cgi?id=6456 Description From pohly 2009-09-27 13:15:48 PST (-) [reply] What information do we want to display to users about backends? In 0.9, "syncevolution --version" didn't print anything about them. In the current "master", it prints: Scanning backend libraries in backends/ Scanning backend libraries in backends/addressbook/.libs/ Scanning backend libraries in backends/file/.libs/ Scanning backend libraries in backends/evolution/.libs/ Scanning backend libraries in backends/sqlite/.libs/ I think for end users it would be more useful to print the backends which were really loaded. Congwu, can you change this for 0.9.1? Note that I fixed a memory handling problem in SyncSourceBackendsInfo/Debug() and turned the functions into static methods of SyncSource, like the related createSource() method. I don't think we have a version number for backends. If we had, this should also go into this output. In 1.0 perhaps? ------- Comment #1 From Chen Congwu 2009-09-27 19:07:45 PST (-) [reply] ------- Pushed to libsyncevo branch ------- Comment #2 From Chen Congwu 2009-09-27 19:08:26 PST (-) [reply] ------- (In reply to comment #0) We don't have version number for backends. ------- Comment #3 From pohly 2009-09-28 05:21:55 PST (-) [reply] ------- (In reply to comment #2) Let's implement this in 1.0. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.