| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi everyone, |
| 5 |
|
| 6 |
Portage currently has two hard-coded lists of variables that control |
| 7 |
the behavior of env-update. I'd like to make these variables |
| 8 |
configurable so that package maintainers have direct control over |
| 9 |
them. The variables break down into two basic types: colon |
| 10 |
separated and space separated. |
| 11 |
|
| 12 |
What is the best way to propagate information about these two |
| 13 |
variable types? For example, we can have a list of variable names |
| 14 |
stored in a new variable called "COLON_SEPARATED" that will reside |
| 15 |
in either the profiles or /etc/env.d/ itself. Variable names not |
| 16 |
listed in COLON_SEPARATED can be assumed to be space separated. |
| 17 |
Does anyone have any ideas to share about how this information |
| 18 |
should be propagated? |
| 19 |
|
| 20 |
Zac |
| 21 |
-----BEGIN PGP SIGNATURE----- |
| 22 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 23 |
|
| 24 |
iD8DBQFFBL92/ejvha5XGaMRAiHfAKDyJF1z4cHw6ErlVpgsBH+wrxJK7QCgneJN |
| 25 |
nADDSpdtyyi0FjhvIK0eXk8= |
| 26 |
=AKoP |
| 27 |
-----END PGP SIGNATURE----- |
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives