| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Danny van Dyk wrote: |
| 5 |
> Am Montag, 11. September 2006 03:44 schrieb Zac Medico: |
| 6 |
>> Hi everyone, |
| 7 |
>> |
| 8 |
>> Portage currently has two hard-coded lists of variables that control |
| 9 |
>> the behavior of env-update. |
| 10 |
> The same applies to eselect env. |
| 11 |
> |
| 12 |
>> I'd like to make these variables |
| 13 |
>> configurable so that package maintainers have direct control over |
| 14 |
>> them. The variables break down into two basic types: colon |
| 15 |
>> separated and space separated. |
| 16 |
> Wrong, there is another type of var, namely those which are not |
| 17 |
> cummultative(sp?). |
| 18 |
|
| 19 |
Okay, then how about if COLON_SEPARATED and SPACE_SEPARATED are |
| 20 |
represent cumulative variables, while all other variables are |
| 21 |
considered non-cumulative? |
| 22 |
|
| 23 |
>> What is the best way to propagate information about these two |
| 24 |
>> variable types? For example, we can have a list of variable names |
| 25 |
>> stored in a new variable called "COLON_SEPARATED" that will reside |
| 26 |
>> in either the profiles or /etc/env.d/ itself. Variable names not |
| 27 |
>> listed in COLON_SEPARATED can be assumed to be space separated. |
| 28 |
>> Does anyone have any ideas to share about how this information |
| 29 |
>> should be propagated? |
| 30 |
> a) You'd need two variables to store that info, as we have 3 classes |
| 31 |
> of envvars. |
| 32 |
> b) This is in no way related to the package tree. Those vars don't |
| 33 |
> magically change their class from colon separated to non |
| 34 |
> cummultative. I'd like to keep it hardcoded, as loading of such |
| 35 |
> variables can go wrong and you'd end up without a working env tool. |
| 36 |
|
| 37 |
We can store them in /etc/env.d/ itself. The env-update tool could |
| 38 |
be hare coded to consider COLON_SEPARATED and SPACE_SEPARATED as |
| 39 |
being implicitly within the SPACE_SEPARATED class. The tool would |
| 40 |
make one pass to accumulate those two variables, and then another |
| 41 |
pass to process the rest of the variables. |
| 42 |
|
| 43 |
Zac |
| 44 |
|
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 47 |
|
| 48 |
iD8DBQFFBYVD/ejvha5XGaMRAojeAKDxFNYaAk668XhmXVjELQVl5PppsACfX0/n |
| 49 |
Wmlxhwj+taaQ0H/aXoIswXI= |
| 50 |
=mLCw |
| 51 |
-----END PGP SIGNATURE----- |
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives