Anthony Gorecki posted <[EMAIL PROTECTED]>, excerpted below, on Sat, 29 Oct 2005 02:56:11 -0700:
> On Saturday, October 29, 2005 02:48, Hamish Marson wrote: >> So what's gone wrong now? I even rmeoved kde & started again, and just >> seem to be back to square one again... > > You're attempting to use the monolithic and segregated KDE packages at the > same time. As far as I know, that isn't supported. > > If you want kmail, for example, just emerge the kmail package. You don't > need kdebase, kdepim, and so forth. Just what I was going to post, but I've some more details/exceptions to add. * Basically, I think you got confused between kde-meta and simple kde. See the last point below, but if some split packages are already merged, you problaby want kde-meta, not plain kde. * Even for the split packages, arts and kdelibs are monolithic, just as they'd be with the full monolithic builds. All the KDE builds depend on kdelibs and if USE=arts, arts. After that, one can merge individual packages as desired and additional dependencies will be pulled in as needed. (Here, with a dual Opteron and kde builds that don't parallelize that well, I'll often run three builds, each with -j3, at once. That won't work with kmail if you use USE=kdeenablefinal tho unless you have LOTS of memory, as with enablefinal active, I watched one particular compile thread climb to something like 780MB at one point (on the kde-3.5-betas, but kmail has been a compile time memory hog for several releases at least), and I'm not even sure that was the max it used, only the max I SAW it use! * I haven't actually tried it, but I /believe/ all you have to do is ensure you don't merge any of the split packages from the specific monolithic package they originate in, to avoid the blockage. kdebase, for one, since it's all basic stuff mostly needed to run the environment or konqueror or as a dependency for other packages anyway, could also probably be merged from monolithic. I believe the devs said that the monolithic packages each provide the packages they include, as well as blocking them, so there should be no dependency problems as long as you don't merge any split packages from a monolithic package you plan to merge. * If you just want everything without spending the time to pick and choose, emerge kde-meta, rather than kde, and it should merge just fine, without blocking on the individual split packages you apparently already have installed. IOW, kde-meta <> kde. The same files are ultimately merged, yes, but kde-meta does it by merging the individual split packages, while kde will attempt to merge the monolithic packages, and will fail with block errors if any of the split packages are already merged. Thus, once you have split packages merged, either use kde-meta, or unmerge all the split packages and merge kde before trying anything else. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
