public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Environment Whitelisting
Date: Mon, 22 Aug 2005 20:27:43 -0400	[thread overview]
Message-ID: <430A6D7F.8020704@egr.msu.edu> (raw)
In-Reply-To: <200508230828.10810.jstubbs@gentoo.org>

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

Jason Stubbs wrote:
> On Tuesday 23 August 2005 06:40, Brian Harring wrote:
> 
>>On Mon, Aug 22, 2005 at 11:33:23PM +0200, Marius Mauch wrote:
>>
>>>Theoretical discussions about this are pointless IMO without
>>>numbers/facts to back things up.
>>
>>I'd posit theroetical discussions about this are pointless without
>>getting ebuild dev's to give a yay/nay on whether they want it or not;
>>not much for trying to force it down their throats if they don't want
>>it (more work, essentially).
> 
> 
> I don't really see what it has to do with ebuild devs... We're talking about 
> the user's environment leaking into the portage build environment, no? 
> Environment vars used by ebuilds can/should be set by users in a portage 
> configuration file rather than being added to the environment. The only 
> issue i see here is user customizations - fex, a hypothetical colorgcc that 
> gets its config info from the env.
> 

Because ebuild devs are the ones doing the maintainance of the
{black,white}lists, and they are the ones who have to futz with them
whenever they want to do funny things.  It's their work to keep things
running smoothly, not ours.  Who wants to foist work on people who
aren't willing to do it?  The lists will just get old and crappy and the
whole system would be useless.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQwptf2zglR5RwbyYAQIhgg//emfko2JdLiibeQc0pmTTY/quD61v6sy0
y5C/VD/EUHSul2ba1so5ZzzXxWMzmwFPdIMRUulisQ2Y7TKRxBTrUu/djQe/tx0p
cGaQekSdLCU0F+4HC2A7bI2kQA1/CspFjETSojyouMXrcM+AMvevIr6+Odf7jfJp
RDkcgzMW14CNjd+nKJ36J/h9Rs17KA5ZU4lnK9MKN9w5wEsw7QtXPyuPgasZ7jx3
H6aOm8WGEP7jiBe/LMYCwaYbb0kElFqUXp/3VyXmuU02vLCHFrTV7oz3LiwfcTi9
MTgwmyzrcBHuMlA5dIxeXGX2icl46KXvsYOhszRjREuUp4F3EqnT+pdwNPqhxCeR
KXbJt8hofYGCvwahoAaxEz6sfv0Jvs8t8BOfDC2FNXYwgSxq2RFRvC2t1iWr+I2f
Phw4m6qZ7QDlz0bgE/Pdnm0TLPolf7+KsoANdJa3lnSXwqrJHR0LhTPJ6GoX82Jw
4woYto47hstVcUWX18dHIQ01ouXgku0++p8eNhLe4B5oKn1Pf5u/tkvdgTS3t/Tb
mrcq+uDy1AWY+lA+W2im/Bbkq9DI551dtlXS4zLO/GX+rs+h+EgtgE0bkwb3f5Q7
mkF58rO6EDBRywvMYxcOzKfHF6f4ty3OQ0i1DrdqIoMFjrCDnNfAODI7YZNF/BWB
D0/VyCA4E2Q=
=q9+h
-----END PGP SIGNATURE-----
-- 
gentoo-portage-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-08-23  0:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 20:25 [gentoo-portage-dev] Environment Whitelisting Alec Warner
2005-08-22  1:24 ` Zac Medico
2005-08-22  3:52 ` [gentoo-portage-dev] " Drake Wyrm
2005-08-22  4:41   ` Zac Medico
2005-08-22 16:29     ` Kristian Benoit
2005-08-22 14:52   ` Jason Stubbs
2005-08-22 18:08     ` Zac Medico
2005-08-22 19:15       ` warnera6
2005-08-22 19:24         ` Zac Medico
2005-08-22 20:58           ` Brian Harring
2005-08-23  1:57           ` Kristian Benoit
2005-08-23  2:15             ` Brian Harring
2005-08-22 21:33 ` [gentoo-portage-dev] " Marius Mauch
2005-08-22 21:40   ` Brian Harring
2005-08-22 21:55     ` warnera6
2005-08-22 21:59     ` Marius Mauch
2005-08-22 22:19       ` Brian Harring
2005-08-22 22:36         ` Alec Warner
2005-08-22 22:41           ` Brian Harring
2005-08-22 23:01             ` [gentoo-portage-dev] Profiles [ was Environmental Whitelisting ] Alec Warner
2005-08-22 23:28     ` [gentoo-portage-dev] Environment Whitelisting Jason Stubbs
2005-08-22 23:56       ` Brian Harring
2005-08-23 10:50         ` Jason Stubbs
2005-08-23  0:27       ` Alec Warner [this message]
2005-08-23  2:46       ` Kristian Benoit
2005-08-23  3:40         ` Alec Warner
2005-08-23 16:19           ` Kristian Benoit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=430A6D7F.8020704@egr.msu.edu \
    --to=warnera6@egr.msu.edu \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox