Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 623854 - sys-apps/portage should provide a way for ebuilds to disable FEATURES=sandbox
Summary: sys-apps/portage should provide a way for ebuilds to disable FEATURES=sandbox
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Ebuild Support (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Portage team
Depends on:
Reported: 2017-07-04 23:44 UTC by Mike Gilbert
Modified: 2017-11-06 20:19 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Mike Gilbert gentoo-dev 2017-07-04 23:44:04 UTC
sandbox has the potential to cause problems with some software. It would be helpful to give some way for ebuilds to opt-out of being sandboxed when they are know to trigger bugs/flaws in sys-apps/sandbox.

Lack of such a mechanism has led to the development of a sandbox escape tool (app-portage/unsandbox). It seems like it would be much simpler to offer some global variable to disable sandbox in the first place.
Comment 1 Mike Gilbert gentoo-dev 2017-07-04 23:48:51 UTC
I'm thinking that a new RESTRICT value might be logical. This would allow sandbox to be disabled in response to USE conditionals as well.
Comment 2 Thomas Deutschmann (RETIRED) gentoo-dev 2017-11-06 10:01:33 UTC
While I was looking for such a functionality more than once I am actually not sure if this would be a good idea: Keep in mind that people may expect something when they set FEATURES="sandbox" or FEATURES="usersandbox". A possibility to allow ebuild maintainer to disable sandbox would clash with user choice and may have undesired impact.

So I think we should only warn in case of known problems like currently happening in dev-db/{mysql,mariadb,percona-server} or sys-apps/coreutils but still allowing users to emerge these packages with sandbox. And in case of a serious issue like infinite running test suite like seen in bug 624012 for sys-block/mbuffer src_test should be skipped or package should fail in first phases like pkg_pretend (but not when doing binary merge in most cases!) if there's a general problem with sandbox and sandbox is activated.