| 1 |
Hi, |
| 2 |
|
| 3 |
is there a specific reason why we want to support dynamic variables |
| 4 |
(ACCT_USER_$foo) at all? |
| 5 |
|
| 6 |
Isn't package.env support enough, i.e. use ACCT_USER_ID from environment |
| 7 |
if set (which we should detect and log, maybe this will require a |
| 8 |
different namespace for the variables at all to be able to differentiate |
| 9 |
between values set by acct-* ebuild and user override)? |
| 10 |
|
| 11 |
Of course this won't allow something like `ACCT_USER_ID=42 emerge |
| 12 |
<package which will pull in multiple acct-user/*>` but I am not sure if |
| 13 |
this is an implementation goal. |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
Regards, |
| 18 |
Thomas Deutschmann / Gentoo Linux Developer |
| 19 |
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 |
Archives