manuals: propose https for SSTATE_MIRRORS
PATCH 1/1 manuals: propose https for SSTATE_MIRRORS
Both http and https work, but https should raise fewer questions from users.
--- documentation/brief-yoctoprojectqs/index.rst | 4 ++-- documentation/overview-manual/concepts.rst | 2 +- documentation/ref-manual/variables.rst | 4 ++-- documentation/sdk-manual/appendix-customizing.rst | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-)
documentation/brief-yoctoprojectqs/index.rst +2 -2
@@ -256,12 +256,12 @@ an entire Linux distribution, including the toolchain, from source. BB_SIGNATURE_HANDLER = "OEEquivHash" BB_HASHSERVE = "auto" BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687" - SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/&YOCTO_DOC_VERSION;/PATH;downloadfilename=PATH" + SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/&YOCTO_DOC_VERSION;/PATH;downloadfilename=PATH" The above settings assumed the use of Yocto Project &YOCTO_DOC_VERSION;. If you are using the development version instead, set :term:`SSTATE_MIRRORS` as follows:: - SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH" + SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH" #. **Start the Build:** Continue with the following command to build an OS image for the target, which is ``core-image-sato`` in this example:
documentation/overview-manual/concepts.rst +1 -1
@@ -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://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ file://.* file:///some/local/dir/sstate/PATH" .. note::
documentation/ref-manual/variables.rst +2 -2
@@ -7196,7 +7196,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/(.*) https://server_url_sstate_path/universal-4.8/\1 \n" If a mirror uses the same structure as :term:`SSTATE_DIR`, you need to add "PATH" at the
@@ -7205,7 +7205,7 @@ system and gives an overview of their function and contents. :: SSTATE_MIRRORS ?= "\ - file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ + file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ file://.* file:///some-local-dir/sstate/PATH" :term:`SSTATE_SCAN_FILES`
documentation/sdk-manual/appendix-customizing.rst +1 -1
@@ -264,7 +264,7 @@ source, you need to do a number of things: to find the configuration. The variable you need to set is :term:`SSTATE_MIRRORS`:: - SSTATE_MIRRORS = "file://.* http://example.com/some_path/sstate-cache/PATH" + SSTATE_MIRRORS = "file://.* https://example.com/some_path/sstate-cache/PATH" You can set the :term:`SSTATE_MIRRORS` variable in two different places:
Signature · 1 line
2.25.1
Quoted 42 lines
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Michael Opdenacker
Sent: den 26 januari 2022 14:18
To: [email protected]
Cc: Michael Opdenacker <[email protected]>
Subject: [docs] [PATCH] manuals: propose https forSSTATE_MIRRORSBoth http and https work, but https should raise fewer questions from users.
Signed-off-by Michael Opdenacker <[email protected]>--- documentation/brief-yoctoprojectqs/index.rst | 4 ++-- documentation/overview-manual/concepts.rst | 2 +- documentation/ref-manual/variables.rst | 4 ++-- documentation/sdk-manual/appendix-customizing.rst | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-)documentation/brief-yoctoprojectqs/index.rst +2
-2@@ -256,12 +256,12 @@ an entire Linux distribution, including the toolchain, from source. BB_SIGNATURE_HANDLER = "OEEquivHash" BB_HASHSERVE = "auto" BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687" - SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/&YOCTO_DOC_VERSION;/PATH;downloadfilename=PATH" + SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/&YOCTO_DOC_VERSION;/PATH;downloadfilename=PATH" The above settings assumed the use of Yocto Project &YOCTO_DOC_VERSION;. If you are using the development version instead, set :term:`SSTATE_MIRRORS` as follows:: - SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH" + SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH" #. **Start the Build:** Continue with the following command to build an OS image for the target, which is ``core-image-sato`` in this example:documentation/overview-manual/concepts.rst +0
-0
documentation/overview-manual/concepts.rst Behind the scenes, the shared state code works by looking in · line 1907
Quoted 5 lines
documentation/overview-manual/concepts.rst +1
-1@@ -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://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
You might want to take this opportunity to remove the no longer needed \n from all these examples.
documentation/ref-manual/variables.rst system and gives an overview of their function and contents. · line 7199
Quoted 13 lines
documentation/overview-manual/concepts.rst +0
-0file://.* file:///some/local/dir/sstate/PATH" .. note::documentation/ref-manual/variables.rst +1
-1@@ -7196,7 +7196,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/(.*) https://server_url_sstate_path/universal-4.8/\1 \n"
Here it is even inconsistent as this example has a \n at the end of the value, which the other examples do not.
Quoted 26 lines
documentation/ref-manual/variables.rst +1
-1If a mirror uses the same structure as :term:`SSTATE_DIR`, you need to add "PATH" at the@@ -7205,7 +7205,7 @@ system and gives an overview of their function and contents. :: SSTATE_MIRRORS ?= "\ - file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ + file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ file://.* file:///some-local-dir/sstate/PATH" :term:`SSTATE_SCAN_FILES`documentation/sdk-manual/appendix-customizing.rst +1
-2@@ -264,7 +264,7 @@ source, you need to do a number of things: to find the configuration. The variable you need to set is :term:`SSTATE_MIRRORS`:: - SSTATE_MIRRORS = "file://.* http://example.com/some_path/sstate-cache/PATH" + SSTATE_MIRRORS = "file://.* https://example.com/some_path/sstate-cache/PATH" You can set the :term:`SSTATE_MIRRORS` variable in two different places: --
Quoted 1 line
2.25.1
//Peter
Hi Peter
Thank you very much for the new review!
Quoted 61 lines · Peter Kjellerstedt
Quoted 42 lines
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Michael Opdenacker
Sent: den 26 januari 2022 14:18
To: [email protected]
Cc: Michael Opdenacker <[email protected]>
Subject: [docs] [PATCH] manuals: propose https forSSTATE_MIRRORSBoth http and https work, but https should raise fewer questions from users.
Signed-off-by Michael Opdenacker <[email protected]>--- documentation/brief-yoctoprojectqs/index.rst | 4 ++-- documentation/overview-manual/concepts.rst | 2 +- documentation/ref-manual/variables.rst | 4 ++-- documentation/sdk-manual/appendix-customizing.rst | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-)documentation/brief-yoctoprojectqs/index.rst +2
-2@@ -256,12 +256,12 @@ an entire Linux distribution, including the toolchain, from source. BB_SIGNATURE_HANDLER = "OEEquivHash" BB_HASHSERVE = "auto" BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687" - SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/&YOCTO_DOC_VERSION;/PATH;downloadfilename=PATH" + SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/&YOCTO_DOC_VERSION;/PATH;downloadfilename=PATH" The above settings assumed the use of Yocto Project &YOCTO_DOC_VERSION;. If you are using the development version instead, set :term:`SSTATE_MIRRORS` as follows:: - SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH" + SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH" #. **Start the Build:** Continue with the following command to build an OS image for the target, which is ``core-image-sato`` in this example:documentation/overview-manual/concepts.rst +0
-0documentation/overview-manual/concepts.rst Behind the scenes, the shared state code works by looking in · line 1907
Quoted 5 lines
documentation/overview-manual/concepts.rst +1
-1@@ -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://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \You might want to take this opportunity to remove the no longer needed \n from all these examples.
Quoted 11 lines
documentation/overview-manual/concepts.rst +0
-0file://.* file:///some/local/dir/sstate/PATH" .. note::documentation/ref-manual/variables.rst +0
-0@@ -7196,7 +7196,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::
Quoted 4 lines
documentation/ref-manual/variables.rst system and gives an overview of their function and contents. · line 7199
Quoted 2 lines
documentation/ref-manual/variables.rst +1
-1- SSTATE_MIRRORS ?= "file://universal-4.9/(.*) http://server_url_sstate_path/universal-4.8/\1 \n" + SSTATE_MIRRORS ?= "file://universal-4.9/(.*) https://server_url_sstate_path/universal-4.8/\1 \n"Here it is even inconsistent as this example has a \n at the end of the value, which the other examples do not.
Right, good catch, but I'd rather fix this through a different commit, possibly touching other settings as well.
I am being programmed not to mix different changes in the same commit ;-)
Cheers
Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com