-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul de Vrieze wrote: > On Monday 11 September 2006 03:44, Zac Medico wrote: >> 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? > > There should also be a third list (or the absense of inclusion in the above). > That is those variables that can only have one value and are overridden > instead of appended.
I think it will be sufficient to have COLON_SEPARATED and SPACE_SEPARATED lists, with all other variables assumed to be overridden instead of appended. To sumarize what I've said in my other replies, COLON_SEPARATED and SPACE_SEPARATED will be stored in /etc/env.d/ itself. The env-update tool (or whatever tool will process /etc/env.d/) will be hard coded to consider COLON_SEPARATED and SPACE_SEPARATED as being implicitly within the SPACE_SEPARATED class. The tool will make one pass to accumulate those two variables, and then another pass to process the rest of the variables. The COLON_SEPARATED and SPACE_SEPARATED variables will automatically be initialized with the old hard coded values. Moving forward, packages that install files in /etc/env.d/ should include COLON_SEPARATED and SPACE_SEPARATED definitions as necessary for the other variables that they define. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFBdf1/ejvha5XGaMRAtzkAKDupzkoiuD5LxyklTr5odvBMoiHxwCfYKYx h3jGTEn6YQhqau17fFhNkKQ= =OUrp -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
