1 |
On Sun, May 18, 2014 at 6:29 PM, Leho Kraav <leho@×××××.com> wrote: |
2 |
|
3 |
> On 19.05.2014 03:11, Leho Kraav wrote: |
4 |
> |
5 |
>> |
6 |
>> Do I now always have to rebuild all the packages to get the new changes |
7 |
>> to user.eclass included? I'd really like to just ignore the environment |
8 |
>> file coming with the binpkg and the let the local system determine |
9 |
>> pretty much everything. Then I could just build the packages once and |
10 |
>> continue developing on binclient. |
11 |
>> |
12 |
>> Option B is if I could just make a list of functions that cannot be |
13 |
>> overriden by later binpkg environment import. In this case egetent, |
14 |
>> enewuser, enewgroup. My preliminary experiments with "declare -r" or |
15 |
>> "readonly" in /etc/portage/bashrc didn't really succeed, probably |
16 |
>> because the processes during binpkg emerge are not related or I just |
17 |
>> don't know the right way to do this. It appears in the beginning, some |
18 |
>> stuff runs from the binclient environment, then everything gets switched |
19 |
>> to binpkg environment, then final cleanup happens again in binclient |
20 |
>> environment. |
21 |
>> |
22 |
>> |
23 |
> ${QA_INTERCEPTORS} looks like something really interesting for this. |
24 |
> Except it looks like it's a hardcoded internal list in bin/ebuild.sh that |
25 |
> cannot be added to with an outside environment variable? |
26 |
> |
27 |
> |
28 |
QA_INTERCEPTORS are meant to detect when certain binaries are called in |
29 |
global scope (which is illegal). I wouldn't rely on them for anything else. |
30 |
|
31 |
-A |