From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5020F13838B for ; Thu, 18 Sep 2014 08:03:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CAA46E099C; Thu, 18 Sep 2014 08:03:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5337CE0992 for ; Thu, 18 Sep 2014 08:03:20 +0000 (UTC) Received: from pomiot.lan (77-253-128-207.adsl.inetia.pl [77.253.128.207]) (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 5BC64340084; Thu, 18 Sep 2014 08:03:18 +0000 (UTC) Date: Thu, 18 Sep 2014 10:02:50 +0200 From: =?ISO-8859-2?B?TWljaGGzIEfzcm55?= To: Bertrand Simonnet Cc: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] [PATCH] per package environment: generalize the mechanism to be profile specific Message-ID: <20140918100250.4543a789@pomiot.lan> In-Reply-To: References: <5411FCB0.9080802@gentoo.org> <54174EA7.2040206@gentoo.org> <54188CE6.5030104@gentoo.org> <20140917232804.163aba5b@pomiot.lan> <541A0090.6050804@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.24; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/tKGeMLL2lRKhkdDcDCozJpg"; protocol="application/pgp-signature" X-Archives-Salt: 9c7ff110-0695-4418-b34c-cb2ae50994c6 X-Archives-Hash: 216799acf1858a59324748bcc24f4df4 --Sig_/tKGeMLL2lRKhkdDcDCozJpg Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Dnia 2014-09-17, o godz. 14:57:10 Bertrand Simonnet napisa=B3(a): > I'd rather use the env/ mechanism instead of the package.env one as it is > more flexible. It depends on what you aim to do. As portage(5) points out, both have their advantages: - package.env is parsed early, and so allows you override more variables, like FEATURES, - env/ is used as bashrc extension. The other difference is that package.env supports any atom syntax that the particular EAPI supports, while env/ has hardcoded list of possibilities. --=20 Best regards, Micha=B3 G=F3rny --Sig_/tKGeMLL2lRKhkdDcDCozJpg Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUGpGtXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOq8wP/ihU1CJXq1L5edFGjWo9oBuD z37IxDRkj/xqzTrd0rjcNK+aCb7Qpo+mzZz9IsTJgQBz/l10ptZLtt7mq38xo4cK Vpfhz5V/h8fZpVFvt6WUFMX4htbQvqVjCM2CZ6LH2SmI+E/vfiOppR456lQHKaR2 ESTdmnfzgAonV1Tp7Ci5d6FbazsE3B8Fs99RWR+3Uv7KbpU4+IHJwEMrY2fkH2JG RYTx5n+452hWrweH4lZyd8vLMWDvQITMaOUurJN8x4DJoPYie/2d36aZzGoco4Ll S2sxg7NK1bCYnGsBUaaD+eBPUWZjlXTMi87go2qfIktQvLoc9ZLXaPRk3F/eKqiG erjvxl6ogxW8rUducRo12X0tAMSWOF2L0dv1Gbwx9n4HjjSjzPi2yqPIenmZmBHR JUAINHi+wc6LMo3O1w6B8sK1AMkJNWHNvUCHFGs4N118eTlc3b7Uia8bfPK+gyXo naUN9EK+kCxs6PTf1Vs0stCfUdSYryxCKm2AA41b52RN3i4U6c9gM8HDQFMEiKhk 0wdqR8GKOV+uQtqLdDTaIgrmOCrRCIvRtyk8jjw0sVVQI44a1nMxC4x6DS5c/4In VvBaUCum3IipggrobEjoBhG+Z/riWA/Zs3oBMf+VJhtQzhDJrQghWT9H90z+FCyG OVQ3PfPpjtYEHA2n6/Jt =Bjgh -----END PGP SIGNATURE----- --Sig_/tKGeMLL2lRKhkdDcDCozJpg--