On 2021-01-06 20:12, Alec Warner wrote:
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?
No.
Assuming we will always stick to same variables,
ACCT_USER_ID
ACCT_USER_GROUPS
ACCT_USER_SHELL
ACCT_USER_HOME
ACCT_USER_NAME
...
You don't have to deal with variable names which could clash with other
stuff. Instead you will only use values which are safe (no need to care
about stuff like underscores)...
Also, because we are always using same variable names, this will add
some kind of consistency and makes documentation easier. Like you can
referrer to same example (template) and just need to adjust values (it's
actually really hard to get people understand that the example for let's
say mail-filter/opendkim requires more than just copying and adjusting
*values*; for instance, we have packages named acct-user/foo but
*username* is actually food -- do they actually need to override via
ACCT_USER_<ACCT-USER-PKGNAME-THEY-WANT-TO-OVERRIDE>_ or
ACCT_USER_<NAME-USED-IN-ACCT-USER-PKG-THEY-WANT-TO-OVERRIDE>_? Sticking
to same variables names will avoid this confusion).
Like said we will probably need to introduce an own namespace to
override via environment variable and be able to detect the override to
have them logged.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
