On Sun, 2007-01-14 at 09:08 -0500, Jesse Keating wrote:
> hpijs, hplip (should be only required when the system has HP
> printers),
HP is a HUGE brand. These should just work, just like all the other printer
drivers pulled in by cups. As to why these are they're own packages, that's
a different issue to bring up.
Of course, it is another question why these daemons have to run by
default and cannot be activated when the right hardware is plugged in.
> bluez-utils, gnome-bluetooth, nautilus-sendto-bluetooth (Maybe
install
> on demand when bluetooth devices are detected?)
Until we have such a system that can do this, we need to include them so that
the hardware Just Works. We don't strip out all the kernel modules, why
would we do the userland too? People expect their hardware to Just Work, and
we should ensure that it does. Until such time that we can detect their
hardware when they try to use it and offer a way to install the software to
support it, we should include it in the spin, and probably install it by
default (note default, can still be unchecked).
I'd propose that the first step in that direction would be to ensure
that daemons are only started when the relevant hardware appears, see
above.
Matthias