linux/poky.git/bitbake/doc, branch langdale

bitbake: fetch2/git: Clarify the meaning of namespace

2023-02-04T10:34:08+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: a40fc6a3f774bcb28cf72701ac146ceb7ae8061a) 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:08+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: 2b4583922de184a2d96324cd4e3f85993341cd14) 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: details about variable flags starting with underscore

2022-11-10T14:43:30+00:00

Fixes [YOCTO #14140] (Bitbake rev: 8a08e207854810b40b53946ec94065a6a560a7a5) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie (cherry picked from commit 0f3e9d87168813ce49995ff04bccdce11c5f7b47) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: doc: bitbake-user-manual: expand description of BB_PRESSURE_MAX variables

2022-10-26T22:02:10+00:00

(Bitbake rev: 72e9847dd578c3cbed52a9c16fea23ebbeef5046) Signed-off-by: Paul Eggleton Signed-off-by: Michael Opdenacker Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake: bitbake: user-manual: inform about spaces in :remove

2022-10-26T22:02:10+00:00

Inform the reader that there should be no need for spaces in the value when using removal override `:remove`. Considering why spaces are used in the other override operators, it might seem obvious that they aren't needed for the removal operator. But, it seems like I'm not the first to be confused about this. Cc: Richard Purdie Cc: Quentin Schulz Cc: Ross Burton Cc: Nicolas Dechesne (Bitbake rev: 0a493a772f83436cbe909de93c157f4ab2d2d136) Signed-off-by: Johan Korsnes Signed-off-by: Alexandre Belloni Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie

bitbake: doc: bitbake-user-manual: Add definition for BB_PRESSURE_MAX variables

2022-09-29T20:24:29+00:00

Add the definitions for the BB_PRESSURE_MAX{CPU|IO|MEMORY} variables in the bitbake varibales glossary. Further information on how to determine a good threshold will be added to the Yocto reference manual in a later commit. (Bitbake rev: c014281f72f4f54ec8e681ef2b8e1080de9ab5cf) Signed-off-by: Aryaman Gupta Signed-off-by: Randy Macleod Signed-off-by: Michael Opdenacker Reviewed-by: Michael Opdenacker Reviewed-by: Quentin Schulz Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: mention pydevshell in OE

2022-09-22T20:40:23+00:00

(Bitbake rev: 3f23140f3b26d81452e345f56ed67d2928ae3a12) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie

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

2022-08-04T16:09:51+00:00

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

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

2022-07-19T09:55:16+00:00

(Bitbake rev: b171aa45fb8518dcfbba315b303a4fe9bf2180c6) Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

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

2022-06-22T21:41:58+00:00

This addresses bug [YOCTO #10098] (Bitbake rev: cca7999586317435d79bf53df4359cdd8bfadff4) Signed-off-by: Michael Opdenacker Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie