Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ecordonnier@snap.com
To: openembedded-core@lists.openembedded.org
Cc: Etienne Cordonnier <ecordonnier@snap.com>
Subject: [PATCH v3 0/3] archiver.bbclass: archive shallow git sources which have no clone
Date: Tue, 17 Nov 2026 13:24:54 +0100	[thread overview]
Message-ID: <20261117122457.435864-1-ecordonnier@snap.com> (raw)

From: Etienne Cordonnier <ecordonnier@snap.com>

As feedback to the v2 of this patch, it was requested to modify the fetcher to ensure that
localpath() exists when do_fetch completes, in order to avoid the need
for special handling in the archiver bbclass.

This v3 series addresses this feedback, and requires the bitbake
change "fetch/git: return the shallow tarball as localpath when there is no clone"

Etienne Cordonnier (3):
  archiver.bbclass: archive shallow git sources which have no clone
  archiver.bbclass: remove .git from original git source archives
  archiver.bbclass: fail on sources which cannot be archived

 meta/classes/archiver.bbclass            | 23 +++++-
 meta/lib/oeqa/selftest/cases/archiver.py | 91 ++++++++++++++++++++++++
 2 files changed, 112 insertions(+), 2 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-11-17 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 12:24 ecordonnier [this message]
2026-11-17 12:24 ` [PATCH v3 1/3] archiver.bbclass: archive shallow git sources which have no clone ecordonnier
2026-11-17 12:24 ` [PATCH v3 2/3] archiver.bbclass: remove .git from original git source archives ecordonnier
2026-11-17 12:24 ` [PATCH v3 3/3] archiver.bbclass: fail on sources which cannot be archived ecordonnier

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=20261117122457.435864-1-ecordonnier@snap.com \
    --to=ecordonnier@snap.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox