Am 17.07.2014 19:38, schrieb Emilio Pozuelo Monfort: > On 17/07/14 14:06, Fabian Greffrath wrote: >> 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? > > Probably not.
Nod. I'd really like to get rid of the -gtk package and the double build. So +1 from my side dropping evince-gtk. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
