From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: philip.lorenz@bmw.de, bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [RFC PATCH] fetch: `touch` mirror tarball stamp files on download
Date: Wed, 02 Sep 2026 10:06:11 +0100 [thread overview]
Message-ID: <ad4a8405a86e9c243dd2748a82f3cb0535f02b8a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260902083232.825826-1-philip.lorenz@bmw.de>
On Wed, 2026-09-02 at 10:32 +0200, Philip Lorenz via lists.openembedded.org wrote:
> The mirror tarball stamp file's mtime is currently only updated on
> creation / initial download. This makes it difficult to detect whether a
> mirror tarball is still relevant in a given build.
>
> Improve this by also `touch`ing the mirror tarball stamp files alongside
> the sources primary stamp file.
This gets a bit tricky as we don't touch every download file at every
download, we only touch the end stamp file.
This would mean we touch mirror files and stamp files but not main
download files and I think brings things into more disparity?
I'm reluctant on more complexity in this area, we already have a lot of
problems with the mirror tarballs and code structure.
I can also think of cases where updating the timestamp may cause things
to re-download the tarballs too since you can't know the content in
advance with many of them. This is perhaps the stronger reason not to
do this.
I was also going to say there shouldn't be hardcoded DL_DIR references
in there but I notice the fetcher has a few too many of them already.
That would be a separate bug/issue :(.
Cheers,
Richard
next prev parent reply other threads:[~2026-09-02 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 8:32 [RFC PATCH] fetch: `touch` mirror tarball stamp files on download Philip Lorenz
2026-09-02 9:06 ` Richard Purdie [this message]
2026-09-02 12:43 ` Philip Lorenz
2026-09-02 15:26 ` [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=ad4a8405a86e9c243dd2748a82f3cb0535f02b8a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=philip.lorenz@bmw.de \
/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