I really didn't know what to label this issue type as, because it's not exactly a bug, but not exactly a feature request either.

I have had a few hiccups, I guess is what I'll call them, that the instructions did not cover, and I haven't noted yet from following the instructions to get the KDE environment set up, as well as the regular stage 3 package. I will note down those issues when I run through another install process later, and contribute what I can, or file a bug report where I can't contribute.

But this particular issue is different from those hiccups that I had. I ran into this same issue while running the Gnome desktop too. I tried installing a KDE app while using Gnome, and that requires the compilation of qtwebengine. I don't mind a long compilation time at all, but this just fails to compile.

I started installing KDE because I thought maybe the KDE installation would come with a setting somewhere, which might prepare the compiler to use less resources, or something just for qtwebengine, so that qtwebengine will compile for me. As you already know, there is no special settings for qtwebengine compilation that are different for a person doing a full KDE desktop install.

The problem for me, is that the 2GB of swap the instructions had me set up, which should normally be more than enough for most things, fills up during compilation, and then the compile phase fails because it runs out of memory to work with. I also have 8GB of RAM. I know that's not a lot to most people, but it's what I have.

Because I do not know what the generally preferred method of going around an issue like this would be; I decided to make another, much larger, partition for swap, just to be used while I compile qtwebengine. I doubt this will be a problem with 122GB of swap. I understand that would be an unreasonable thing to recommend users to do who run into this issue.

Even if there is a binary available that is not compiled specifically for my subarch, I would rather compile it for my subarch. So I was thinking either an additional instruction could be added into the KDE installation instructions that allow users who run into this problem, to finish going through the KDE install guide, and would allow later updates of qtwebengine to compile without further user intervention. Or maybe a script could be added into the install process that switches from using the swap partition, to a swap file in a tmp directory, if the swap partition fills over 75%, copies the contents of what is in swap to that file, and then aborts the compilation only if the temporary swap file's size causes disk space to fill to maybe leaving only 10GB free at any time during compilation, or during the time the swap partitions contents are copying into the temporary swap file. Then the script deletes the file after either compilation succeeds, or fails. Although I imagine that script would take a long time to design, it's just an idea I had.