Hi Dean, > This new version seems to change blueman from being a gtk-only piece of > software to something bound inseparably to gnome.
why is that? The changes in dependencies primarily represent the switch from GTK+ 2 to GTK+ 3 and thus to GObject Introspection, since that's the preferred (or only?) GTK+ 3 Python binding. Here are the changed dependencies: python-gtk2 (>= 2.12) -> gir1.2-gtk-3.0, gir1.2-gdkpixbuf-2.0, gir1.2-glib-2.0, gir1.2-pango-1.0, python-gi-cairo (*) python-notify -> gir1.2-notify-0.7 python-gconf -> gir1.2-gconf-2.0 (**) python-appindicator -> gir1.2-appindicator3-0.1 (*) gdkpixbuf, glib, pango, and cairo were all dependencies of python-gtk2, so there's nothing new here although the list of immediate dependencies got longer (**) gconf shall be dropped in the near future upstream So I can't see any reason for your accusation, but of course you're always welcome to propose ways of avoiding specific dependencies upstream. The focus of blueman are still desktops like Xfce or MATE. Gnome is definitely not a target desktop, since it ships its own bluetooth component. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
