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

[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?

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

[Leho Kraav]

On 19.05.2014 03:11, Leho Kraav wrote:
>
> 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.
>

${QA_INTERCEPTORS} looks like something really interesting for this. 
Except it looks like it's a hardcoded internal list in bin/ebuild.sh 
that cannot be added to with an outside environment variable?

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

[Alec Warner]

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

On Sun, May 18, 2014 at 6:29 PM, Leho Kraav <leho@kraav.com> wrote:

> On 19.05.2014 03:11, Leho Kraav wrote:
>
>>
>> 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.
>>
>>
> ${QA_INTERCEPTORS} looks like something really interesting for this.
> Except it looks like it's a hardcoded internal list in bin/ebuild.sh that
> cannot be added to with an outside environment variable?
>
>
QA_INTERCEPTORS are meant to detect when certain binaries are called in
global scope (which is illegal). I wouldn't rely on them for anything else.

-A

[-- Attachment #2: Type: text/html, Size: 2138 bytes --]