Zac Medico <[EMAIL PROTECTED]> wrote: > Portage currently has two hard-coded lists of variables that control > the behavior of env-update. I'd like to make these variables > configurable so that package maintainers have direct control over > them. The variables break down into two basic types: colon > separated and space separated. > > What is the best way to propagate information about these two > variable types? For example, we can have a list of variable names > stored in a new variable called "COLON_SEPARATED" that will reside > in either the profiles or /etc/env.d/ itself. Variable names not > listed in COLON_SEPARATED can be assumed to be space separated. > Does anyone have any ideas to share about how this information > should be propagated?
Don't forget that the two lists actually break everything into three categories: the "colon separated" lists, the "space separated" lists, and the ones that aren't special (i.e. the ones that just replace the previous value). So, you would still need two lists. -- This message has been brought to you by the letter three.
pgpyr4iOBDBZY.pgp
Description: PGP signature
