@@ -1904,7 +1904,7 @@ Behind the scenes, the shared state code works by looking in
shared state files. Here is an example::
SSTATE_MIRRORS ?= "\
- file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
+ file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
file://.* file:///some/local/dir/sstate/PATH"
.. note::
@@ -7198,7 +7198,7 @@ system and gives an overview of their function and contents.
following maps the local search path ``universal-4.9`` to the
server-provided path server_url_sstate_path::
- SSTATE_MIRRORS ?= "file://universal-4.9/(.*) http://server_url_sstate_path/universal-4.8/\1 \n"
+ SSTATE_MIRRORS ?= "file://universal-4.9/(.*) http://server_url_sstate_path/universal-4.8/\1"
If a mirror uses the same structure as
:term:`SSTATE_DIR`, you need to add "PATH" at the
@@ -7207,7 +7207,7 @@ system and gives an overview of their function and contents.
::
SSTATE_MIRRORS ?= "\
- file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
+ file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
file://.* file:///some-local-dir/sstate/PATH"
:term:`SSTATE_SCAN_FILES`
Since commit 044fb04d in bitbake (fetch2: Allow whitespace only mirror entries) there is no need to separate the entries in SSTATE_MIRRORS with "\n". Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> --- documentation/overview-manual/concepts.rst | 2 +- documentation/ref-manual/variables.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)