I saw kdebase fail after it *completely finished building* because of ACCESS DENIED errors that were output when the code tried to create /root/.kde/share/config (why the mkdir failed, I do not know). There where a slew of such errors, one from each time that something in the build process tried to refer to this directory. Fortunately, I was building binary packages, so I just continued the emerge with the -k option and the build went on after installing kdebase from the binary package (which is hopefully OK -- I'll check soon). The next package, kdeartwork, started to have the same errors, so I manually created the /root/.kde/share/config directory and it has not complained since. Reproducible: Always Steps to Reproduce:
hi, do you use sudo emerge kde? than this is a duplicate of bug #11664. please also look into bug #7853. thanks.
You are indeed correct that I use sudo for my root work (I do it that way because the root account is setup to be very minimal so that it works even if no non-root filesystems are mounted). I'll do some checking into this (soon) to see if I can see why this makes a difference. I apologize for not finding bug 11664 or 7853 in my searches before filing this bug report. I hadn't realized that the description text was treated as a comment. I'll know better next time.
ok, if you find any fix for kde.eclass to work with sudo, report it in bug #11664 :) thanks so far. *** This bug has been marked as a duplicate of 11664 ***
