public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Environment Whitelisting
Date: Mon, 22 Aug 2005 17:19:15 -0500	[thread overview]
Message-ID: <20050822221915.GV10816@nightcrawler> (raw)
In-Reply-To: <20050822235954.4aece5d1@andy.genone.homeip.net>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

On Mon, Aug 22, 2005 at 11:59:54PM +0200, Marius Mauch wrote:
> On 08/22/05  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).
> 
> That too. But providing them with some numbers will certainly have an
> effect on their decision (especially if it shows that it doesn't really
> affect them ;)
Rather hard to back it up though, without specialized knowledge in 
(effectively) the whole tree- either we do it, or we ask nicely those 
who are supposed to have such knowledge :)

I can rattle off a couple of env vars that screw things up, but how 
many of us are aware that an exported ARCH screws with kernel builds 
fex?

I'd punt it to them, and find out what they think (tiz the route I 
took when I brought this up last).

Explicit whitelisting is great for getting closer to deterministic 
builds, but it's a helluva overhead on a side note.
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-22 22:20 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 [this message]
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
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=20050822221915.GV10816@nightcrawler \
    --to=ferringb@gentoo.org \
    --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