On Wed, Jan 6, 2021 at 11:05 AM Patrick McLean <chutz...@gentoo.org> wrote: > > On Wed, 6 Jan 2021 15:02:12 +0100 > Thomas Deutschmann <whi...@gentoo.org> wrote: > > > Hi, > > > > is there a specific reason why we want to support dynamic variables > > (ACCT_USER_$foo) at all? > > > > Isn't package.env support enough, i.e. use ACCT_USER_ID from environment > > if set (which we should detect and log, maybe this will require a > > different namespace for the variables at all to be able to differentiate > > between values set by acct-* ebuild and user override)? > > > > Of course this won't allow something like `ACCT_USER_ID=42 emerge > > <package which will pull in multiple acct-user/*>` but I am not sure if > > this is an implementation goal. > > This is so ACCT_USER_$foo can be set in make.conf, and not have to > be specified as an environment variable whenever portage is run. This > helps when automated systems are building Gentoo images or systems. >
Not sure I follow. Whether your automation sets a variable in /etc/portage/make.conf or /etc/portage/package.env; it's basically the same problem space; no? -A
