Bugs reported:
https://bugzilla.redhat.com/show_bug.cgi?id=957727
https://bugzilla.redhat.com/show_bug.cgi?id=957733
Tim said he will look at them when he has the time, and he isn't so keen on
making cups depend on samba-client. On the other hand, not having
samba-client installed by default and not providing the user with a good
error message/automatic installation of missing components is rather bad.
On Sat, Apr 27, 2013 at 3:26 PM, Elad Alfassa <elad(a)fedoraproject.org>wrote:
I recently discovered that if I have a printer attached to a Windows
machine (and shared via samba), it'll unusable on default install, because
samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after
the driver prompt dialog it gave a cryptic error message and did not
install the printer.
After installing samba-client, adding a samba network printer worked as
expected. Therefor I suggest we add samba-client to our default
installation, it's only 1.2MB.
Ideally I think it should be added as a Requires in control-center's spec
file, but we could add it to comps instead. If you think adding this to the
default install is a bad idea, control-center should install it with
packagekit whenever users tries to add a Samba printer.
On a related (printing) note, I think it would also make sense to have
hpijs as a default as well, to support more printers.
--
-Elad Alfassa.
--
-Elad Alfassa.