You’re right regarding python-appindicator and python-launchpad-integration. However, since I am using quickly for package creation, these dependencies are created automatically, and switching to manual dependency management would mean quite some additional effort. Therefore, I’d suggest you patch debian/control to remove these dependencies or make them optional (Recommends). The code is (or should be) written in a way that it does not depend on these modules being available.
syncevolution-evolution, however, is not a hard dependency, it has an OR dependency with syncevolution-dbus. The former is the upstream package name, while the latter should be the package name in Ubuntu/Debian. Do you experience any issues with installation when syncevolution-dbus is installed?
As a side note: There is also a GTK3 branch, which I plan to merge into master around the Precise release, so that my PPA has GTK3 packages available for Precise. You might consider packaging that for Unstable.
You’re right regarding python-appindicator and python- launchpad- integration. However, since I am using quickly for package creation, these dependencies are created automatically, and switching to manual dependency management would mean quite some additional effort. Therefore, I’d suggest you patch debian/control to remove these dependencies or make them optional (Recommends). The code is (or should be) written in a way that it does not depend on these modules being available.
syncevolution- evolution, however, is not a hard dependency, it has an OR dependency with syncevolution-dbus. The former is the upstream package name, while the latter should be the package name in Ubuntu/Debian. Do you experience any issues with installation when syncevolution-dbus is installed?
As a side note: There is also a GTK3 branch, which I plan to merge into master around the Precise release, so that my PPA has GTK3 packages available for Precise. You might consider packaging that for Unstable.