Summary: | sys-apps/portage: add ability to disable SOCKSv5-over-UNIX-socket proxy | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nikoli <nikoli> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS, PATCH |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/gentoo/portage/commit/8fd09dc9a25fb673426340a23794df7f11a44010 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 484436 | ||
Attachments: | patch |
Description
Nikoli
2015-05-05 19:41:53 UTC
Created attachment 402766 [details, diff]
patch
Attached patch works fine for me with portage-2.2.18: it builds, all tests work fine, FEATURES='-network-sandbox network-sandbox-proxy', FEATURES='network-sandbox network-sandbox-proxy' and FEATURES='network-sandbox' work as expected.
For me 'python3.3 /usr/lib/portage/python3.3/socks5-server.py /var/tmp/.portage.27962.net.sock' is now running only when both network-sandbox and network-sandbox-proxy are enabled. It should also run when network-sandbox and distcc are enabled, but i did not check.
applied in git commit 1f94508e9adeffd7170cb23852ae40fc1f8b6c98 Released in portage-2.2.19 |