Package: evince-gtk Version: 3.12.1-1 Severity: minor Hi all,
I wonder if a separate evince-gtk package is still necessary at all. If I am not mistaken, evince has only two more package dependencies than evince-gtk: libnautilus-extension1a and libsecret-1-0. Since evince-gtk identifies itself as "evince without GNOME keyring support", I guess it is the second dependency that is meant to get removed by the separate build. However, libsecret-1-0 has only two additional dependencies that aren't pulled in by evince[-gtk] anyway: libgcrypt11 and libsecret-common, of which the latter is an Arch: all package without further dependencies. The libnautilus-extension1a package in turn pulls in libselinux1. So, is this it? Do we really need a separate binary package of evince to avoid the installation of four leaf packages? - Fabian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
