From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: chris.laplante@agilent.com,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH 0/3] Remove bb.fetch compatibility shim module
Date: Fri, 21 Aug 2026 22:27:28 +0100 [thread overview]
Message-ID: <e9b1c5a8825756040472ac48bfbb61db4009ac31.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM8PR12MB54303D8EC454EA621D9171028BA32@DM8PR12MB5430.namprd12.prod.outlook.com>
On Fri, 2026-08-21 at 17:26 +0000, Chris Laplante via lists.openembedded.org wrote:
> Hi Alex,
>
> > On Fri, 21 Aug 2026 at 19:06, Chris Laplante via lists.openembedded.org
> > <chris.laplante=agilent.com@lists.openembedded.org> wrote:
> > > fetch2 replaced fetch a long time ago (2012) so I argue it is time to
> > > say goodbye the bb.fetch shim.
> >
> > Why not instead rename fetch2 to fetch and drop the unneeded '2'? Is there a
> > reason to keep the number?
>
> I thought about it, but I'd bet 'fetch2' is more prevalent than
> 'fetch' in third-party layers. We also document the naming choice:
> https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#file-download-support
> . So I think it would result in breaking a bunch of layers. Whereas
> if people are still using bb.fetch, we can point to the manual if
> they complain.
>
> That being said, I'm not opposed to going the 'fetch' route if people
> prefer it.
I'd probably lean towards moving to "bb.fetch" but leaving fetch2
working for a short while as things get updated. The "2" is fairly
meaningless.
The key question is whether we'd ever have a fetch3 but I suspect we'd
handle things differently with fetcher changes than that...
Cheers,
Richard
prev parent reply other threads:[~2026-08-21 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 17:06 [PATCH 0/3] Remove bb.fetch compatibility shim module chris.laplante
2026-08-21 17:06 ` [PATCH 1/3] bin/bitbake-setup: use bb.fetch2, not bb.fetch chris.laplante
2026-08-21 17:06 ` [PATCH 2/3] lib: " chris.laplante
2026-08-21 17:06 ` [PATCH 3/3] lib: remove bb.fetch shim module; cleanup fallout chris.laplante
2026-08-21 17:17 ` [bitbake-devel] [PATCH 0/3] Remove bb.fetch compatibility shim module Alexander Kanavin
2026-08-21 17:26 ` chris.laplante
2026-08-21 21:27 ` Richard Purdie [this message]
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=e9b1c5a8825756040472ac48bfbb61db4009ac31.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=chris.laplante@agilent.com \
/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.