Aniket and I had a brief conversation just now. Here's a summary; 1. Porting to TelepathyGLib is necessary. Understanding of Telepathy is challenged by how it operates as a DBus service. My post on 8th March http://lists.sugarlabs.org/archive/sugar-devel/2019-March/056365.html describes how to use dbus-monitor to watch the communication between the Telepathy API and the Telepathy service processes.
2. Sugar doesn't have a "make uninstall" target. This makes it hard to test changes. Options are (a) use the install log, (b) touch a marker file and use find to list the files installed, (c) use checkinstall. Other developers may benefit from a working uninstall target. 3. Alternative to using "make uninstall" and "make install" cycles is to edit the source files in place on a test VM, or use rsync to copy them from your git repository to the VM over SSH, rsync -r --checksum src/jarabe $HOST:/usr/local/lib/pythonN.M/dist-packages/ rsync -r --checksum extensions $HOST:/usr/local/share/sugar/ 4. in general if you can't test code within three to ten seconds of saving a source file, you can spend some time to make tools to speed that up. 5. Datastore is also hard to test because it is a DBus service. The old one must be stopped, then removed, before a new one is installed and started. There's probably useful information from the DBus project about how to do it differently. -- James Cameron http://quozl.netrek.org/ _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel