From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] deprecation of SANDBOX_DISABLED
Date: Wed, 28 Sep 2005 03:05:35 -0500 [thread overview]
Message-ID: <20050928080535.GK30337@nightcrawler> (raw)
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
Hola.
Subject says it all; SANDBOX_DISABLED functions as (essentially)
RESTRICT="sandbox", except sandbox is left on for pkg_setup .
This is pretty much redundant, considering it's usage. People stick
it in the global scope; if you _must_ turn off the sandbox for a
specific phase, use SANDBOX_ON=0/1 instead. If you need to disable
sandbox across the board, restrict="sandbox" is your friend.
Since there are still ebuilds in the tree that would be schmooked by
it, it's not going to hit in the coming version, but I'd expect it to
be dead next version after unless people have a really good reason why
it should live on.
So... thoughts? Yes it's minor, but it's a matter of cleaning
up/simplifying portage code, and removing redundancy.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-09-28 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 8:05 Brian Harring [this message]
2005-10-04 4:12 ` [gentoo-dev] deprecation of SANDBOX_DISABLED Martin Schlemmer
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=20050928080535.GK30337@nightcrawler \
--to=ferringb@gentoo.org \
--cc=gentoo-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