Declare proxy_config obsolete
Since 7b18e5ec3b
, which was released with 0.19.0, proxy_config has no
effect anymore. No one seems to have missed it, likely because setting
the proxies via the config file was a mistake anyway. The environment
variables are the proper way.
Declare these config entries officially obsolete and warn if they still
hang around in some legacy config. We will drop them from the schema in
one of the next releases.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
This commit is contained in:
parent
15de0142d4
commit
635b1023a1
@ -63,8 +63,8 @@ Environment variables
|
||||
| ``SSTATE_DIR`` | the bitbake environment. |
|
||||
| ``TMPDIR`` | |
|
||||
+--------------------------+--------------------------------------------------+
|
||||
| ``http_proxy`` | This overwrites the proxy configuration in the |
|
||||
| ``https_proxy`` | configuration file. |
|
||||
| ``http_proxy`` | These variables define the proxy configuration |
|
||||
| ``https_proxy`` | bitbake should use. |
|
||||
| ``ftp_proxy`` | |
|
||||
| ``no_proxy`` | |
|
||||
+--------------------------+--------------------------------------------------+
|
||||
|
@ -418,11 +418,3 @@ Configuration reference
|
||||
* ``<local-conf-id>``: string [optional]
|
||||
A string that is added to the ``local.conf``. It operates in the same way
|
||||
as the ``bblayers_conf_header`` entry.
|
||||
|
||||
* ``proxy_config``: dict [optional]
|
||||
Defines the proxy configuration bitbake should use. Every entry can be
|
||||
overwritten by the respective environment variables.
|
||||
|
||||
* ``http_proxy``: string [optional]
|
||||
* ``https_proxy``: string [optional]
|
||||
* ``no_proxy``: string [optional]
|
||||
|
@ -93,6 +93,10 @@ def load_config(filename):
|
||||
__file_version__, version_value),
|
||||
filename)
|
||||
|
||||
if config.get('proxy_config'):
|
||||
logging.warning('Obsolete ''proxy_config'' detected. '
|
||||
'This has no effect and will be rejected soon.')
|
||||
|
||||
return config
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user