Stacking order of use-flag defaults/overrides differ between portage and pkgcore

[nexon]

In portage, specifying a use-flag in make.conf overrides make.defaults and package.use in the profiles In pkgcore, it only overrides make.defaults in the profiles, while the user-specified package.use overrides the package.use in the profiles.

Honestly, i would expect something like this regarding ordering: profile/make.defaults -> user/make.conf -> profile/package.use -> ebuild/IUSE (EAPI-1) -> user/package.use -> profile/package.force -> profile/package.mask -> profile/package.use.force -> profile/package.use.mask

Although since that's not the way portage does it, I guess that's a moot point. I couldn't find anything about the stacking order of use-flags in PMS either, but i didn't look very hard.

[nexon]

Ignore profile/package.force and profile/package.mask in my expected ordering. And ebuild/IUSE should be before profile/package.use since certain platforms might have different needs than the ebuild-maintainer.

I fail