I'm afraid, that the fix for bug 70345 does not resolve the problem, as the parent profiles has to applied in opposite direction (from general to specialiced) in contrast to how it is applied now. From my understanding, to solve the problem, 1. a list of all applicable profiles (from specialiced till general) has to be determined , e.g. /usr/portage/profiles/default-linux/x86/2005.0 /usr/portage/profiles/default-linux/x86 /usr/portage/profiles/default-linux /usr/portage/profiles/base 2. the relevant files from these profiles have to sourced consecutive from general to specialiced, e.g. /usr/portage/profiles/base /usr/portage/profiles/default-linux /usr/portage/profiles/default-linux/x86 /usr/portage/profiles/default-linux/x86/2005.0 Reproducible: Always Steps to Reproduce: 1. 2. 3.
It's true that the specialised profiles are read before the general profiles, but when ufed then reads the general profiles, it sticks whatever flags (in make.defaults or use.mask) it finds there before the flags from the specialised profiles, so that the specialised profiles' flags still override them. This should get everything right. If it does not, can you give a specific example of where it goes wrong?
Oh, and just to make sure, you are talking about 0.36, right? 0.35-r2 and -r3 do indeed have bugs, which 0.36 is supposed to fix.
This bug has been reported against ufed 0.35-r2. After update to ufed 0.36, the evaluation of cascaded profiles seems to be corrected.
Okay, this can be closed, then. Thanks for the report.
