From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] whitelisting the env ebuilds execute in
Date: Mon, 14 Mar 2005 14:21:53 -0500 [thread overview]
Message-ID: <20050314192153.GA19241@kaf.zko.hp.com> (raw)
In-Reply-To: <20050313154016.GC19847@freedom.wit.com>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Brian Harring wrote: [Sun Mar 13 2005, 10:40:16AM EST]
> So... yeah. Anyone got a good reason why all vars should be dumped
> into the ebuild environment? I don't see the point in all of my
> binpkgs having my ECHANGELOG_USER setting, for example.
Sounds like a great idea to me.
Regards,
Aron
--
Aron Griffis
Gentoo Linux Developer
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-14 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 15:40 [gentoo-dev] whitelisting the env ebuilds execute in Brian Harring
2005-03-13 15:48 ` Ciaran McCreesh
2005-03-13 16:04 ` Brian Harring
2005-03-13 22:20 ` Ned Ludd
2005-03-13 23:05 ` Brian Harring
2005-03-13 23:24 ` Thomas de Grenier de Latour
2005-03-15 9:03 ` Sven Vermeulen
2005-03-14 19:21 ` Aron Griffis [this message]
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=20050314192153.GA19241@kaf.zko.hp.com \
--to=agriffis@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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