ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-19 21:07:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
def4ca3905
crosstool-ng/config/global/download.in

184 lines
4.8 KiB
Plaintext
Raw Normal View History

Split-up download and extract options into two separate files, because download options are begining to be numerous. /trunk/config/global/extract.in | 193 1 192 0 ---------------------------------------------- /trunk/config/global/download.in | 52 1 51 0 ------------ /trunk/config/global.in | 3 2 1 0 + 3 files changed, 4 insertions(+), 244 deletions(-)
2008-07-19 21:22:58 +00:00
# Options specific to downloading packages
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
comment "Downloading"
config FORCE_DOWNLOAD
bool
prompt "Force downloads"
default n
help
Force downloading tarballs, even if one already exists.
Usefull if you suspect a tarball to be damaged.
config ONLY_DOWNLOAD
bool
prompt "Stop after downloading tarballs"
default n
help
Only download the tarballs. Exit once it done.
Usefull to pre-retrieve the tarballs before going off-line.
Add a new option to set connection timeout while downloading. /trunk/scripts/functions | 16 8 8 0 ++++++++-------- /trunk/config/global/download_extract.in | 25 25 0 0 +++++++++++++++++++++++++ 2 files changed, 33 insertions(+), 8 deletions(-)
2008-05-06 20:30:49 +00:00
config CONNECT_TIMEOUT
int
prompt "connection timeout"
default 10
help
From the curl manual:
Maximum time in seconds that you allow the connection to the server to take.
The scenario is as follows;
- some enterprise networks have firewalls that prohibit FTP traffic, while
still allowing HTTP
- most download sites have http:// equivalent for the ftp:// URL
- after this number of seconds, it is considered that the connection could
not be established, and the next URL in the list is tried, until we reach
an URL that will go through the firewall, most probably an http:// URL.
If you have a slow network, you'd better set this value higher than the default
10s. If you know a firewall is blocking connections, but your network is globally
fast, you can try to lower this value to jump more quickly to allowed URLs. YMMV.
Note that this value applies equally to wget if you have that installed.
Of course, you'd be better off to use a proxy, as offered by the following
choice of options.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
choice
bool
prompt "Proxy type"
One-liner to fix default proxy config. /trunk/config/global/download_extract.in | 2 1 1 0 +- 1 file changed, 1 insertion(+), 1 deletion(-)
2008-05-03 17:56:40 +00:00
default PROXY_TYPE_NONE
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PROXY_TYPE_NONE
bool
prompt "No proxy"
help
Select this option if you have a direct connection to the internet,
or if you already set the environment adequately.
config PROXY_TYPE_HTTP
bool
prompt "HTTP proxy"
help
Use an HTTP proxy to connect to to the internet.
Only the http and ftp protocols will be tunneled through this
proxy.
Alternatively to setting this option, you can set and export the
following variables in your environment:
ftp_proxy=http://user:passwd@proxy.server:port/
http_proxy=http://user:passwd@proxy.server:port/
https_proxy=http://user:passwd@proxy.server:port/
# Haha! Here is an interesting feature/bug of mconf!
# The following config entries will be shown out-side the
# choice menu!
# To add a third entry in the choice menu, add it after the
# if...endif conditional below, and so on for a fourth entry...
if PROXY_TYPE_HTTP
config PROXY_HOST
string
prompt "hostname/IP"
config PROXY_PORT
int
prompt "port"
Try to make clear that SOCKS proxying is currently BROKEN. /trunk/config/global/download_extract.in | 36 19 17 0 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-)
2008-04-20 16:46:17 +00:00
default 8080
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PROXY_USER
string
prompt "user name"
config PROXY_PASS
string
prompt "password"
endif # USE_HTTP_PROXY
config PROXY_TYPE_SOCKS
bool
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
prompt "SOCKS 4/5 proxy (EXPERIMENTAL)"
depends on EXPERIMENTAL
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
Use a Socks 4/5 proxy to connect to the internet.
All protocols can get tunneled through this kind of proxy (depending
Un-mark Socks proxy settings as BROKEN. /trunk/config/global/download_extract.in | 16 4 12 0 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-)
2008-06-20 14:00:01 +00:00
on your proxy configuration, some do not allow all protocols, but
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
chances are that protocols needed by crosstool-NG are allowed).
Try to make clear that SOCKS proxying is currently BROKEN. /trunk/config/global/download_extract.in | 36 19 17 0 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-)
2008-04-20 16:46:17 +00:00
Alternatively to setting this option, you can configure tsocks
system-wide, and set and export the following variable in your
environment:
LD_PRELOAD=/path/to/your/tsocks-library.so
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
This option makes use of the tsocks library. You will have to have tsocks
installed on your system, of course.
If you think you do not know what tsocks is, or how to configure it,
chances are that you do not need to set this option.
if PROXY_TYPE_SOCKS
choice
bool
prompt "type"
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
default PROXY_TYPE_SOCKS_SYS
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
config PROXY_TYPE_SOCKS_SYS
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
bool
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
prompt "Use system settings"
help
Try to make clear that SOCKS proxying is currently BROKEN. /trunk/config/global/download_extract.in | 36 19 17 0 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-)
2008-04-20 16:46:17 +00:00
Use that if tsocks is already configured on your system.
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
config PROXY_TYPE_SOCKS_AUTO
bool
Un-mark Socks proxy settings as BROKEN. /trunk/config/global/download_extract.in | 16 4 12 0 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-)
2008-06-20 14:00:01 +00:00
prompt "Auto"
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
help
Try to make clear that SOCKS proxying is currently BROKEN. /trunk/config/global/download_extract.in | 36 19 17 0 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-)
2008-04-20 16:46:17 +00:00
crosstool-NG will attempt to guess what type of SOCKS version
the proxy speaks.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PROXY_TYPE_SOCKS_4
bool
Un-mark Socks proxy settings as BROKEN. /trunk/config/global/download_extract.in | 16 4 12 0 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-)
2008-06-20 14:00:01 +00:00
prompt "SOCKS 4"
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
config PROXY_TYPE_SOCKS_5
bool
Un-mark Socks proxy settings as BROKEN. /trunk/config/global/download_extract.in | 16 4 12 0 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-)
2008-06-20 14:00:01 +00:00
prompt "SOCKS 5"
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
endchoice
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
if ! PROXY_TYPE_SOCKS_SYS
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PROXY_HOST
string
prompt "hostname/IP"
config PROXY_PORT
int
prompt "port"
Try to make clear that SOCKS proxying is currently BROKEN. /trunk/config/global/download_extract.in | 36 19 17 0 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-)
2008-04-20 16:46:17 +00:00
default 1080
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PROXY_USER
string
prompt "user name"
config PROXY_PASS
string
prompt "password"
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
endif # ! PROXY_TYPE_SOCKS_SYS
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
endif # USE_SOCKS_PROXY
endchoice
config PROXY_TYPE
string
Using SOCKS 4/5 proxy is no easy task: - a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate) - tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection - SOCKS proxies are expected to be in 'local' networks - there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed. /trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++---- /trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------ 2 files changed, 77 insertions(+), 14 deletions(-)
2008-04-18 22:16:28 +00:00
default "none" if PROXY_TYPE_NONE
default "http" if PROXY_TYPE_HTTP
default "sockssys" if PROXY_TYPE_SOCKS_SYS
default "socksauto" if PROXY_TYPE_SOCKS_AUTO
default "socks4" if PROXY_TYPE_SOCKS_4
default "socks5" if PROXY_TYPE_SOCKS_5
Reference in New Issue Copy Permalink