Bug#763560: gnome-core: please do not depend on vino

[Christoph Anton Mitterer]

Package: gnome-core
Version: 1:3.8+8
Severity: wishlist


Hi.

IMHO, metapackages should usually not be allowed to have
hard depends, since when "components" of the meta package
depend on each other, they'd already have these dependencies
themselves.

I can only think of very few examples where metapackages
should actually have hard dependencies, namely when the
components don't depend on each other, but the whole functionality
represented by the package depends on both.
But even in those cases, Recommends should be fully enough.


I know the maintainers see this different, and even when they're
wrong it's ultimately up to them to decide (at least unless
tech-ctte overrules as with NM), nevertheless, please reconsider
it for the following:

vino shouldn't be a hard depdency, actually wouldn't even think it
qualifies for Recommends.


gnome-core should be really just that: core, and while I can
understand that this includes editor, terminal, filebroweser or
control panel - a VNC server has really nothing to do in this group.

The functionality of it (AFAIU) is per default anyway disabled so
by forcing users to install it, you don't gain anything.
And even if - the concept of remote assistence is pretty uncommon
in Linux and Debian.


Even when not enabled per default, having a VNC server installed
bears always the risk of it being accidentally activated.
VNC is highly insecure, which should be reason enough not to install
it by default - but even if you insist for what ever reason to have
it instaled by default, Recommends should be fully enoguh so that
anyone who doesn't want it can decide againt.


Cheers,
Chris.