Hello, Matijs van Zuijlen, le Tue 05 Aug 2014 21:11:31 +0200, a écrit : > This latest version of the python-pyatspi package depends on both > at-spi2-core and qt-at-spi,
Yes, this is on purpose. > In the common case, only one of these desktops is installed and it > makes no sense to pull in part of the other. It makes a lot of sense for a user to be told that e.g. kedit is nice, and try to install and run it from his gnome desktop, or vice-versa with gedit. Or taking other more convincing examples, it makes a lot of sense for a user to install and use vlc (just like he used to use it on Windows...) on a Gnome desktop, or gimp (just like he used to use it on Windows...) on a KDE dekstop. > I suppose another option would be to create separate > python-pyatspi-gnome and python-pyatspi-kde packages. Average users have no idea what qt/kde vs gtk means (in particular blind people who can not even see the difference...), and thus they won't know which one they would have to install a particular package in order to get access to some software. Actually, qt-at-spi even happens to depend on at-spi2-core in the end, so the question is about the additional packages brought by qt-at-spi. The raw figure is, starting from a bare system without even the standard task, plus at-spi2-core, 38MiB brought by installing qt-at-spi. But that includes fontconfig, libice6 and other such stuff that will typically be brought by a gnome destkop. Measuring only the extra qt libs gives only 25MiB. Is that saving really worth the pain of a user wondering why this or that application is not accessible at all? Samuel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
