[gentoo-dev] Is it possible to ignore / override parts of binpkg environment locally?

[Leho Kraav]

Hi all


Scenario: I'm developing yet another bootstrapping process for whatever 
reason. Let's say the project needs some changes made to user.eclass. I 
make the changes, set eclass-overrides, do my test bootstrapping run, 
build all the packages.

Then on the binclient, it turns out something needs more work and I have 
to change user.eclass some more.

Do I now always have to rebuild all the packages to get the new changes 
to user.eclass included? I'd really like to just ignore the environment 
file coming with the binpkg and the let the local system determine 
pretty much everything. Then I could just build the packages once and 
continue developing on binclient.

Option B is if I could just make a list of functions that cannot be 
overriden by later binpkg environment import. In this case egetent, 
enewuser, enewgroup. My preliminary experiments with "declare -r" or 
"readonly" in /etc/portage/bashrc didn't really succeed, probably 
because the processes during binpkg emerge are not related or I just 
don't know the right way to do this. It appears in the beginning, some 
stuff runs from the binclient environment, then everything gets switched 
to binpkg environment, then final cleanup happens again in binclient 
environment.

Ideas?