On Tue, Mar 06, 2012 at 10:20:13PM +0100, Christian PERRIER wrote: > Quoting Olaf van der Spek ([email protected]): > > On Tue, Mar 6, 2012 at 9:44 PM, Christian PERRIER <[email protected]> > > wrote: > > > Quoting Olaf van der Spek ([email protected]): > > > > > >> > workgroup question belongs to samba-common I have to admit that the > > >> > question shouldn't be asked when people only install samba-common just > > >> > because it's pulled as a dependency (I wonder which one). > > >> > > >> samba-common samba-common-bin smbclient > > > > > > OK, so next step..:-)...what is bringing smbclient in?
> > Don't know, the desktop task? > > When removing samba it only removed those 3 pkgs. > Hmmm, I don't understand, indeed. > The desktop task doesn't itself pull smbclient or samba > *directly*. Those are pulled...but only by the "file-server" task and, > here, I think the workgroup question makes perfect sense. > So, if you're only installing the desktop task: > - first the samba *binary* package shouldn't be installed at all > - then we need to find out what triggers smbclient, in order to check > whether it can be droped entirely or not I would guess that it's cups-client pulling in smbclient as a Recommends that lands this in the desktop task. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
