All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcio Henriques" <marciohenriques84@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake: add BB_GIT_SHALLOW_SKIP_FAST to disable fast shallow mode
Date: Tue, 05 May 2026 01:08:52 -0700	[thread overview]
Message-ID: <1413912.1777968532263348828@lists.openembedded.org> (raw)
In-Reply-To: <b49490a4a2e1cbbbdd8eb84d3c5bb2af57418488.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

Hello,

We want to create a download mirror to store all sources needed to build a
specific project.

The idea is to use Git shallow tarballs because each tarball has a unique name.
This prevents files from being overwritten in the mirror. With full Git
tarballs, the name is always the same, so the mirror file gets replaced each
time. If something is removed from the upstream repository, we might upload a
new tarball that no longer contains a reference used by a recipe that was
already integrated.

With shallow tarballs, we can safely clean DL_DIR since it's not the source of
truth. If something is removed from upstream, we fall back to the mirror and
use the shallow tarball.

For most of the builds, we want to use the bare clone in DL_DIR/git2 and just
update the repo when bumping a SRCREV. The DL_DIR/git2 repositories are
available on the machine that triggers the build.

The shallow tarball is a fallback for cases where something was removed from
the repository (for example, after a force push) and is not present in
DL_DIR/git2 or upstream, but was merged at some point. This is why we use Git
shallow and set shallow_skip_fast to True.

Best regards,
Marcio

[-- Attachment #2: Type: text/html, Size: 1526 bytes --]

  reply	other threads:[~2026-05-05  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 12:38 [PATCH 0/1] Subject: [RFC PATCH] bitbake: fetch2/git: add switch to disable fast shallow path Marcio Henriques
2026-04-30 12:38 ` [PATCH 1/1] bitbake: add BB_GIT_SHALLOW_SKIP_FAST to disable fast shallow mode Marcio Henriques
2026-04-30 15:22   ` [bitbake-devel] " Antonin Godard
2026-05-01  9:29   ` Richard Purdie
2026-05-05  8:08     ` Marcio Henriques [this message]
2026-05-05  9:41       ` Richard Purdie
2026-05-11 16:14         ` Marcio Henriques
2026-05-12  8:15           ` [bitbake-devel] " Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1413912.1777968532263348828@lists.openembedded.org \
    --to=marciohenriques84@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.