linux/poky.git/bitbake/doc, branch yocto-4.0.14

bitbake: fetch2/git: Clarify the meaning of namespace

2023-02-04T10:34:05+00:00

Namespace in this context means a branch, a tag, etc., clarify it in the description. Also, fix a typo "a any", replace with plain "any". This patch is based of feedback on new applied patch d32e5b0e ("fetch2/git: Prevent git fetcher from fetching gitlab repository metadata") (Bitbake rev: 86f2fa5261da959cda706c794a0047e5e89d4d6b) Signed-off-by: Marek Vasut Signed-off-by: Richard Purdie (cherry picked from commit b4999425c812b25cb359d5163d11e3c1b030dc28) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: fetch2/git: Prevent git fetcher from fetching gitlab repository metadata

2023-02-04T10:34:05+00:00

The bitbake git fetcher currently fetches 'refs/*:refs/*', i.e. every single object in the remote repository. This works poorly with gitlab and github, which use the remote git repository to track its metadata like merge requests, CI pipelines and such. Specifically, gitlab generates refs/merge-requests/*, refs/pipelines/* and refs/keep-around/* and they all contain massive amount of data that are useless for the bitbake build purposes. The amount of useless data can in fact be so massive (e.g. with FDO mesa.git repository) that some proxies may outright terminate the 'git fetch' connection, and make it appear as if bitbake got stuck on 'git fetch' with no output. To avoid fetching all these useless metadata, tweak the git fetcher such that it only fetches refs/heads/* and refs/tags/* . Avoid using negative refspecs as those are only available in new git versions. Per feedback on the ML, Gerrit may push commits outsides of branches or tags during CI runs, which currently works with the 'nobranch=1' fetcher parameter. To retain this functionality, keep fetching everything in case the 'nobranch=1' is present. This still avoids fetching massive amount of data in the common case, since 'nobranch=1' is rare. Update 'nobranch' documentation. Reviewed-by: Peter Kjellerstedt (Bitbake rev: c17fc1468ab84663b919e2809606b1b8ea2bebd9) Signed-off-by: Marek Vasut Signed-off-by: Alexandre Belloni (cherry picked from commit d32e5b0ec2ab85ffad7e56ac5b3160860b732556) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: npm fetcher: improve description of SRC_URI format

2022-09-16T16:53:22+00:00

Using the term "Parameter" which is consistent with the description of SRC_URI parameters in the following text. (Bitbake rev: ac576d6fad6bba0cfea931883f25264ea83747ca) Signed-off-by: Michael Opdenacker Reported-by: Quentin Schulz Reviewed-by: Quentin Schulz Signed-off-by: Luca Ceresoli (cherry picked from commit 87e42f1202162152c779ccc8bbd06f88f0bdab96) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: bitbake: bitbake-user-manual: hashserv can be accessed on a dedicated domain

2022-09-16T16:53:22+00:00

(Bitbake rev: b7967aa086ee3f3716a17431af0eef05452fb46f) Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni (cherry picked from commit b171aa45fb8518dcfbba315b303a4fe9bf2180c6) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: doc: bitbake-user-manual: document npm and npmsw fetchers

2022-09-16T16:53:22+00:00

This addresses bug [YOCTO #10098] (Bitbake rev: 04fdbca2005702e79d69aa56861a085f845178e2) Signed-off-by: Michael Opdenacker Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie (cherry picked from commit cca7999586317435d79bf53df4359cdd8bfadff4) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: doc: bitbake-user-manual: add explicit target for crates fetcher

2022-09-16T16:53:22+00:00

Like in other sections describing fetchers (Bitbake rev: bcbe78bbaea0312d61f31f4a51b2bc9e672f1cb7) Signed-off-by: Michael Opdenacker Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie (cherry picked from commit c9bab35f6aecbf85ee1a19a7b70e15a80b42471f) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: Correct description of the ??= operator

2022-09-16T16:53:22+00:00

Stating that the assignment is done at the end of parsing is misleading. The weak default value is the value which a variable will expand to if no value has been assigned to it using any of the assignment operators. (Bitbake rev: f28dbdf80a7fc2febca227f8cb2b474f5058281e) Signed-off-by: Jacob Kroon Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie (cherry picked from commit 8189f58d0449d16f162b6e8d98c4e5edc6bff875) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: bitbake: bitbake-user-manual: punctuation fixes

2022-03-30T12:05:03+00:00

- Replace hyphens by em dashes when necessary See https://www.grammarly.com/blog/hyphens-and-dashes/ - No uppercase after em dashes - No uppercase after colons if what follows is not a complete sentence. - Fix spacing before colons ":" - Replace em-dashes with colons for consistency in a section (Bitbake rev: 72230d6a9976b3bfca1f1e6fb09736fec195e2fe) (Bitbake rev: f1c4ac816e927f490fb9852c12aa408e8c9403b1) Signed-off-by: Michael Opdenacker Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake: doc: bitbake-user-manual: branch parameter now mandatory in git SRC_URIs

2022-03-26T09:27:43+00:00

(Bitbake rev: 981d1929937519cd98200a6ef291d97a16d358ad) Signed-off-by: Michael Opdenacker Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake: doc: bitbake-user-manual: add branch parameter to git SRC_URI examples

2022-03-26T09:27:43+00:00

This parameter is now required by the git fetcher module (Bitbake rev: d61b349581c219e7f9d50f683177184fa473cb83) Signed-off-by: Michael Opdenacker Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie