On Tuesday 08 September 2009 15:14:40 Volker Armin Hemmann wrote: > On Dienstag 08 September 2009, Alan McKinnon wrote: > > On Tuesday 08 September 2009 14:56:35 Volker Armin Hemmann wrote: > > > On Dienstag 08 September 2009, Alan McKinnon wrote: > > > > On Tuesday 08 September 2009 14:14:27 Volker Armin Hemmann wrote: > > > > > On Dienstag 08 September 2009, Massimiliano Ziccardi wrote: > > > > > > equery d bluez did not return anything... > > > > > > > > > > > > localhost ~ # equery d bluez > > > > > > [ Searching for packages depending on bluez... ] > > > > > > localhost ~ # > > > > > > > > > > > > Any other idea? > > > > > > > > > > > > Thank you!! > > > > > > > > > > yes, get rid of wicd and its dependencies. > > > > > > > > No, he doesn't need to do that. gksu is one of three options: > > > > > > > > RDEPEND=" > > > > > > > > || ( x11-misc/ktsuss x11-libs/gksu kde-base/kdesu ) > > > > > > > > So he probably wants to do this: > > > > > > > > emerge -av1 kdesu > > > > emerge -avuND world > > > > > > > > This works. I know it works. I have wicd and I do not have gksu and > > > > emerge doesn't feel inclined to tell me to get gksu. > > > > > > the problem is that gksu is already installed. He has to remove that > > > and all its deps or emerge will always try to pull in bluez-libs. > > > > So why are you telling him to get rid of wicd? > > because wicd was/is pulling in gksu on his system, which is pulling in > nautilus, which is pulling in a lot of other stuff.
Which conflicts with this prior statement of yours: "the problem is that gksu is already installed" If it's already installed, it will pull in bluez. It's in the dep tree not because he wants wicd, but because it is already present. wicd works just fine without gksu. It will use kdesu, which is also fine as he wants to merge kde-meta -- alan dot mckinnon at gmail dot com
