From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: AUTOREV with SRCREV_module? (Re: [OE-core] [PATCH] u-boot: set git repo branch with SRCBRANCH)
Date: Fri, 4 Apr 2025 14:26:32 +0300 [thread overview]
Message-ID: <Z-_B6GF31Zad_xjE@nuoska> (raw)
In-Reply-To: <CANNYZj_rH+zUJ1gVGPQ-MvkAnX6941bWUSKKpYLtOnDboJqgoQ@mail.gmail.com>
Hi,
On Fri, Apr 04, 2025 at 01:07:21PM +0200, Alexander Kanavin wrote:
> I have to note that poky-bleeding is not tested in any way, so you
> probably first want to stop using it, or otherwise propose a test
> plan.
poky-bleeding.bbclass could have some trivial tests. I can try to draft
them. I don't expect oe-core to test it with real SW components.
I plan to use it with some SW components I care about. Finding
and fixing issues from bleeding edge pre-release builds can help
improve releases and reduce maintenance and integration work later on.
This could be more work, or the same amount of work but just done
by developers closer to the SW component upstream which could help
distro maintainers. I find poky-bleeding.bbclass useful.
FWIW, my question seems to be answered by SRCREV_FORMAT and
patch will be:
--- a/meta-poky/classes/poky-bleeding.bbclass
+++ b/meta-poky/classes/poky-bleeding.bbclass
@@ -12,6 +12,10 @@ python pokybleeding_version_handler () {
if "pseudo" in bpn:
bb.warn("Here 5 %s %s" % (d.getVar("PN"), bpn))
d.setVar("SRCREV", "${AUTOREV}")
+ srcrev_format = d.getVar("SRCREV_FORMAT")
+ if srcrev_format:
+ for multi_scm in d.getVar("SRCREV_FORMAT").split("_"):
+ d.setVar("SRCREV_%s" % multi_scm, "${AUTOREV}")
if "+git" not in d.getVar("PV"):
d.appendVar("PV", "+git")
}
Cheers,
-Mikko
prev parent reply other threads:[~2025-04-04 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18330E36E620F155.22125@lists.openembedded.org>
2025-04-04 10:53 ` AUTOREV with SRCREV_module? (Re: [OE-core] [PATCH] u-boot: set git repo branch with SRCBRANCH) Mikko Rapeli
2025-04-04 11:07 ` Alexander Kanavin
2025-04-04 11:26 ` Mikko Rapeli [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=Z-_B6GF31Zad_xjE@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.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 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.