I'm not sure if I'd read thigns right but is that going to be the case? If so then why?

I don't have any official knowledge, but since K3B will be the CD/DVD burner in 5.0 Standard, the kdelibs will have to be included. I think that's all that's needed to get K3B working, not the whole KDE bundle.

As I understand it, K3B will be included because the other burners have proved unsatisfactory for one reason or another. And indeed, K3B is a terrific program.--GrannyGeek

Ahh. Had wondered as I recall the discussion shortly before the 5.1 release going towards bundling kdelibs, but finally desciding not due to graveman being a good solution for vetor-standard. To be honest, while it isn't k3b, it is a good front-end to the odd assortment of programs that works behind the gui.

Still, k3b is, from what i can see, The Program to use for burning in linux.

Ahh. Had wondered as I recall the discussion shortly before the 5.1 release going towards bundling kdelibs, but finally desciding not due to graveman being a good solution for vetor-standard. To be honest, while it isn't k3b, it is a good front-end to the odd assortment of programs that works behind the gui.

I think I heard that Graveman had gone into the grave, i.e., development had stopped. So eventually the program would have to be replaced like it or not.--GrannyGeek

On my machine, I've not been able to get xfburn to work (at all) on any of the beta's or rc's for 5.9. So I'm plenty happy about K3b being added. Kdelibs really isn't that big. A portion of the libs is needed to run the KDM login manager anyway.

Amarok will also ask you for kdebase, when you install it from the repo.However, if you unmark kdebase in gslapt (or use --no-dep in slapt-get), Amarok works just fine.I think kdebase is only needed for Konqueror integration, so you shouldn't lose anything if you skip it (at least, nothing I have noticed).