1 |
On Wed, 6 Jan 2021 15:02:12 +0100 |
2 |
Thomas Deutschmann <whissi@g.o> wrote: |
3 |
|
4 |
> Hi, |
5 |
> |
6 |
> is there a specific reason why we want to support dynamic variables |
7 |
> (ACCT_USER_$foo) at all? |
8 |
> |
9 |
> Isn't package.env support enough, i.e. use ACCT_USER_ID from environment |
10 |
> if set (which we should detect and log, maybe this will require a |
11 |
> different namespace for the variables at all to be able to differentiate |
12 |
> between values set by acct-* ebuild and user override)? |
13 |
> |
14 |
> Of course this won't allow something like `ACCT_USER_ID=42 emerge |
15 |
> <package which will pull in multiple acct-user/*>` but I am not sure if |
16 |
> this is an implementation goal. |
17 |
|
18 |
This is so ACCT_USER_$foo can be set in make.conf, and not have to |
19 |
be specified as an environment variable whenever portage is run. This |
20 |
helps when automated systems are building Gentoo images or systems. |