I have kde 3.4.1 installed from the kde-3.4.1.ebuild fine. Wanted to switch to split ebuilds. I added all components to package.keywords. Changed kde-base/kde to kde-base/kde-meta in the world file. No matter what I do, I get blocks saying kde-base/kdebase blocks (kscreensaver) for example. No matter which meta module I pick there are blocks. KDE is no longer package masked that I can see. What would be nice is instructions for migrating FROM monolithic ebuilds TO split ebuilds WITHOUT having to uninstall and rebuild KDE from scratch. Right now, switching to split ebuilds is very complex for non-developers. JM2C Reproducible: Always Steps to Reproduce: 1. Edit world and change kde to kde-meta 2. add all kde-3.4.1* modules to package.keywords with ~x86 3. try to emerge -u kde{module}-meta Actual Results: any module blocks applications and gentoo seems to want to compile each component module even though it had been installed! Expected Results: Documentation on switching to split ebuilds from monolithic would be helpful for non-developers so that the entire suite does not have to be reinstalled. IMHO the setup for split ebuilds is WAY to hackish. find /usr/portage/kde-base -name '*3.4.1.ebuild' -printf "=kde-base/%f\n" | sed s/.ebuild/'* \t~x86' should not have to be done. Simply putting the parent -meta package name in package.keywords should be enough IMO.
KDE folks, any pointers on this? There's a bit information on how to use split ebuilds in the KDE Configuration guide (http://www.gentoo.org/doc/en/kde-config.xml) but nothing about the migration process itself.
It could make sense to add a paragraph to explain better the migration process, but surely it won't tell how to migrate from the monolithic ebuilds to the splitted ones without recompiling everything, because that's impossible. In fact, the instruction for the migration from one monolithic version of KDE to the same version, but splitted, would just be instruction on how to uninstall the former and install the latter (in a scenario where all the ebuilds are stable and there's no need to tinker with package.keywords).
Thanks at least for confirming that there is _NO_ migration path from monolithic to split ebuilds from w/in the same KDE version. Perhaps that should itself be noted to save others from the head-banging experience I had! :). It should be made clear that once a compile and install choice is made, it is pretty permanent. In the documentation, it cryptically says that both monolithic and split ebuilds can co-exist. This could use some clarification. For example, monolithic KDELIBS could co-exist with split-ebuild of kdepim, network, utils, etc. But I would not think that is wise. I suppose now I must wait for at least a new minor version, i.e. 3.4.2 to try the split ebuilds.
> Thanks at least for confirming that there is _NO_ migration path from > monolithic to split ebuilds from w/in the same KDE version. There's a path. It just involves first uninstalling each monolithic KDE ebuild before emerging the matching -meta ebuild, so for short periods of time pieces of KDE go missing. Doing it overnight is a good idea. You can also merge the split ebuilds, using emerge -O to ignore the blocking deps, and then unmerge the monolithic ones. But you do have to remember to unmerge them manually, so I don't know if we should recommend this. You'd also have to first note and emerge all deps from outside kde-base. Either way, it'd be nice to update the split ebuilds FAQ wrt upgrading. > In the documentation, it cryptically says that both monolithic and > split ebuilds can co-exist. This could use some clarification. For example, > monolithic KDELIBS could co-exist with split-ebuild of kdepim, network, > utils, etc. But I would not think that is wise. The exact text in the howto is: "Split and monolithic ebuilds can be mixed freely. The only restriction is that a monolithic ebuild can't be installed at the same time as a split ebuild deriving from it. There are blocking deps in the ebuilds that enforce this, so you can do anything emerge allows you to do." Meaning that if you install eg monolithic kdebase, you can also install the split kmail (from kdepim), but you can't install the split konqueror (from kdebase). So you can create any meaningful mix. It's perfectly safe and supported. There's no such thing as a split kdelibs... There's only one kdelibs ebuild.
Created attachment 62425 [details, diff] Diff to kde-split-ebuilds.xml This diff adds a brief section about upgrading from the monolithic ebuilds. There's little new info, just clarifying and bringing things together. However, this means the sections on installation, upgrade and 'split and monolithic ebuild interoperability' are slightly overlapping, so a reorg might be in order eventually.
Yes, it is brief, but accurate and succinct. I would also add the suggestion that it is NOT necessary to convert to split ebuilds, and it would be perfectly fine to pick up the split ebuilds with the next major release of KDE.
We'd rather users converted earlier than later because we want to phase out the monolithic ebuilds at some point (kde4...) and we don't want to have too many people still using monolithic ebuilds at that point. There are also benefits to be gained from switching to the split ebuilds. Anyway, IMHO the howto already states clearly that for kde 3.4, split and monolithic ebuilds are both supported.
Okay, patch applied. I'll mark this one as FIXED, perhaps if there is a need for reorganising the guide we'll open a new bug for it.
