From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
	by nuthatch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-16788-garchives=archives.gentoo.org@gentoo.org>)
	id 1GMat6-0003TT-1X
	for garchives@archives.gentoo.org; Mon, 11 Sep 2006 01:47:04 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8B1kYCh006620;
	Mon, 11 Sep 2006 01:46:34 GMT
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8B1ifNL022332
	for <gentoo-dev@lists.gentoo.org>; Mon, 11 Sep 2006 01:44:41 GMT
Received: from [192.168.24.6] (ip68-5-234-231.oc.oc.cox.net [68.5.234.231])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTP id 2B5B5646AE
	for <gentoo-dev@gentoo.org>; Mon, 11 Sep 2006 01:44:41 +0000 (UTC)
Message-ID: <4504BF77.2020502@gentoo.org>
Date: Sun, 10 Sep 2006 18:44:23 -0700
From: Zac Medico <zmedico@gentoo.org>
User-Agent: Thunderbird 1.5.0.5 (X11/20060719)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] colon separated variables in /etc/env.d/
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Archives-Salt: d347b380-2205-43dd-83c1-a3b6aaf6c49c
X-Archives-Hash: 88a68c64116e72e21a9ac84e8e0748fb

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi everyone,

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?

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFBL92/ejvha5XGaMRAiHfAKDyJF1z4cHw6ErlVpgsBH+wrxJK7QCgneJN
nADDSpdtyyi0FjhvIK0eXk8=
=AKoP
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list