From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto@lists.yoctoproject.org, ext-antti.garding@kempower.com
Subject: Re: [yocto] Modifying SRC_URI before it is parsed by the fetcher
Date: Tue, 12 May 2026 18:13:41 +0200 [thread overview]
Message-ID: <3306fb96-8964-4eea-be32-27fd26385bb0@cherry.de> (raw)
In-Reply-To: <AS8PR08MB7251242FD5DCEDE2DFA4374FD5392@AS8PR08MB7251.eurprd08.prod.outlook.com>
Hi Antti,
On 5/12/26 6:05 PM, EXT-Antti Gärding via lists.yoctoproject.org wrote:
> You don't often get email from ext-antti.garding=kempower.com@lists.yoctoproject.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
>> Please explain the problem first, before presenting the various
> solution attempts. What do you need to modify in SRC_URI and why?
> Maybe there's a completely different approach to the actual issue.
>
> I want to add a tag parameter to one of the URIs under certain conditions so that bitbake can check that the commit matching the rev parameter has that tag. The tag check is already there in bitbake.
>
Which conditions?
The following pseudocode could help (untested).
def src_uri_tag(d):
if conditions:
return ';tag=' + mytag
return ''
SRC_URI_TAG = "${@src_uri_tag(d)}"
SRC_URI = "git://someforge.co/myrepo.git;branch=main${SRC_URI_TAG}"
Cheers,
Quentin
next prev parent reply other threads:[~2026-05-12 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 14:47 Modifying SRC_URI before it is parsed by the fetcher EXT-Antti Gärding
2026-05-12 15:07 ` [yocto] " Alexander Kanavin
2026-05-12 16:05 ` EXT-Antti Gärding
2026-05-12 16:13 ` Quentin Schulz [this message]
2026-05-13 6:26 ` EXT-Antti Gärding
2026-05-13 6:38 ` ChenQi
2026-05-13 12:35 ` EXT-Antti Gärding
2026-05-13 12:42 ` Alexander Kanavin
2026-05-13 12:51 ` EXT-Antti Gärding
2026-05-13 13:11 ` EXT-Antti Gärding
2026-05-13 13:51 ` Alexander Kanavin
2026-05-13 14:22 ` EXT-Antti Gärding
2026-05-13 14:35 ` Alexander Kanavin
2026-05-13 15:07 ` EXT-Antti Gärding
2026-05-13 15:32 ` Quentin Schulz
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=3306fb96-8964-4eea-be32-27fd26385bb0@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=ext-antti.garding@kempower.com \
--cc=yocto@lists.yoctoproject.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.