From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Srinuvasan Arjunan <srinuvasan_a@mentor.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] meta/conf/bitbake.conf: enable SRCPV support for AUTOREV
Date: Fri, 14 Apr 2023 14:42:13 +0530 [thread overview]
Message-ID: <CAB2Z2nOKKT3XYQ4qkNz+E6gMKxuyMoWBmo_LN70h4+vR2d7fQA@mail.gmail.com> (raw)
In-Reply-To: <b58e37e2-00db-d2db-9955-cdcce8ae3f26@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
On Fri, Apr 14, 2023 at 2:30 PM 'Jan Kiszka' via isar-users <
isar-users@googlegroups.com> wrote:
> On 14.04.23 10:57, Srinuvasan Arjunan wrote:
> > From: Srinuvasan A <srinuvasan_a@mentor.com>
> >
> > One of our downstream project recipe uses `SRCREV = "${AUTOREV}"` to get
> > the latest changes always, but this not works after bitbake 2 migration,
> > it throws the below error.
> >
> > do_fetch: Fetcher failure: Recipe uses a floating tag/branch without a
> fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for
> OE).
> >
> > Till now we don't have support for SRCPV in ISAR, hence add this support
> > as like OE.
> >
> > Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
> > ---
> > meta/classes/base.bbclass | 4 ++++
> > meta/conf/bitbake.conf | 4 ++++
> > 2 files changed, 8 insertions(+)
> >
> > diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> > index 53550ae..819f8a2 100644
> > --- a/meta/classes/base.bbclass
> > +++ b/meta/classes/base.bbclass
> > @@ -120,6 +120,10 @@ root_cleandirs() {
> > python() {
> > import re
> >
> > + srcuri = d.getVar('SRC_URI')
> > + if srcuri:
> > + d.setVar("SRCPV", "${@bb.fetch2.get_srcrev(d)}")
> > +
>
> Still not the logic that OE uses - why?
>
> Jan
>
I thought it would be enable when SRC_URI contains any SCM
They have a logic like get the uri and validating the uri.scheme against
with many SCM , and set the needsrcrev variable if needed
f.e : git
if uri.scheme in ("git", "gitsm"):
needsrcrev = True
Would we need to check like this?
>
> --
> Siemens AG, Technology
> Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to the Google Groups
> "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/b58e37e2-00db-d2db-9955-cdcce8ae3f26%40siemens.com
> .
>
[-- Attachment #2: Type: text/html, Size: 4843 bytes --]
next prev parent reply other threads:[~2023-04-14 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 10:17 Srinuvasan Arjunan
2023-04-13 7:02 ` Jan Kiszka
2023-04-13 7:09 ` Srinuvasan Arjunan
2023-04-14 8:57 ` Srinuvasan Arjunan
2023-04-14 9:00 ` Jan Kiszka
2023-04-14 9:12 ` Srinuvasan Arjunan [this message]
2023-04-14 9:16 ` Jan Kiszka
2023-04-17 13:27 ` Srinuvasan Arjunan
2023-04-17 14:10 ` Jan Kiszka
2023-04-18 6:25 ` Srinuvasan Arjunan
2023-04-18 7:06 ` Uladzimir Bely
2023-04-19 2:40 ` [PATCH v2] " Srinuvasan Arjunan
2023-04-19 13:43 ` Jan Kiszka
2023-05-08 17:57 ` Anton Mikanovich
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=CAB2Z2nOKKT3XYQ4qkNz+E6gMKxuyMoWBmo_LN70h4+vR2d7fQA@mail.gmail.com \
--to=srinuvasanasv@gmail.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan_a@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox