I believe it does (or at least the libfetch intermediate). Or at least that seems to be what is implied by the issue tracker.FETCH supports socks5, does PKG piggyback on it?
pkg_env : {
http_proxy: "{http://10.0.0.1:8080}"
https_proxy: "{https://10.0.0.1:8080}
}
pkg.conf
documentation (PKG.CONF(5)) says:PKG_ENV: Key/Value list
This tells pkg(8) to set key/values to be passed in the
environment. This allow setting variables to configure
the http(s) fetcher. Which accepts environment variables
compatible with fetch(3), e.g., HTTP_PROXY. Default: not
set.
SOCKS5_PROXY Uses SOCKS version 5 to make connection. The for-
mat must be the IP or hostname followed by a colon
for the port. IPv6 addresses must enclose the ad-
dress in brackets. If no port is specified, the
default is 1080. This setting will supercede a
connection to an HTTP_PROXY.
socks5
, thus the former as well supports it. Am I wrong? pkg.conf
?PKG_ENV {
SOCKS5_PROXY=localhost:12000
}
Code:PKG_ENV { SOCKS5_PROXY=localhost:12000 }
Thanks...![]()
:
after pkg_env
, which needs to be in lowercase. try:pkg_env: {
SOCKS5_PROXY=localhost:12000
}