public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] buildhistory-collect-srcrevs: Adapt to the new variable override syntax
Date: Thu, 26 Aug 2021 17:57:18 +0000	[thread overview]
Message-ID: <54cf0ace72d74dfb923843ff19baa2e4@axis.com> (raw)
In-Reply-To: <CA+chaQdRQVF5X86t7ghv2vNrLH+oyL_fHiSL-sq8YPWPm=4SPg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2948 bytes --]

Hmm, you are of course correct. New patch coming.

//Peter

From: Martin Jansa <martin.jansa@gmail.com>
Sent: den 26 augusti 2021 19:45
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Patches and discussions about the oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] buildhistory-collect-srcrevs: Adapt to the new variable override syntax

Is this one correct? The '_' in SRCREV_%s should IMHO stay and only the '_' in _pn should be replaced with ':'.

As the first case in the SRC_URI element name, not an override.

On Thu, Aug 26, 2021 at 7:28 PM Peter Kjellerstedt <peter.kjellerstedt@axis.com<mailto:peter.kjellerstedt@axis.com>> wrote:
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com<mailto:peter.kjellerstedt@axis.com>>
---
 scripts/buildhistory-collect-srcrevs | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/scripts/buildhistory-collect-srcrevs b/scripts/buildhistory-collect-srcrevs
index bca01a922b..6c919299a6 100755
--- a/scripts/buildhistory-collect-srcrevs
+++ b/scripts/buildhistory-collect-srcrevs
@@ -53,7 +53,7 @@ def main():
         sys.exit(1)

     if options.forcevariable:
-        forcevariable = '_forcevariable'
+        forcevariable = ':forcevariable'
     else:
         forcevariable = ''

@@ -78,14 +78,14 @@ def main():
                             value = splitval[1].strip('" \t\n\r')
                         if line.startswith('# SRCREV = '):
                             orig_srcrev = value
-                        elif line.startswith('# SRCREV_'):
+                        elif line.startswith('# SRCREV:'):
                             splitval = line.split('=')
-                            name = splitval[0].split('_')[1].strip()
+                            name = splitval[0].split(':')[1].strip()
                             orig_srcrevs[name] = value
                         elif line.startswith('SRCREV ='):
                             srcrev = value
-                        elif line.startswith('SRCREV_'):
-                            name = splitval[0].split('_')[1].strip()
+                        elif line.startswith('SRCREV:'):
+                            name = splitval[0].split(':')[1].strip()
                             srcrevs[name] = value
                 if srcrev and (options.reportall or srcrev != orig_srcrev):
                     all_srcrevs[curdir].append((pn, None, srcrev))
@@ -99,7 +99,7 @@ def main():
             print('# %s' % curdir)
             for pn, name, srcrev in srcrevs:
                 if name:
-                    print('SRCREV_%s_pn-%s%s = "%s"' % (name, pn, forcevariable, srcrev))
+                    print('SRCREV:%s:pn-%s%s = "%s"' % (name, pn, forcevariable, srcrev))
                 else:
                     print('SRCREV:pn-%s%s = "%s"' % (pn, forcevariable, srcrev))




[-- Attachment #2: Type: text/html, Size: 7821 bytes --]

      reply	other threads:[~2021-08-26 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 17:28 [PATCH 1/2] bitbake.conf: Use the new variable override syntax in a comment Peter Kjellerstedt
2021-08-26 17:28 ` [PATCH 2/2] buildhistory-collect-srcrevs: Adapt to the new variable override syntax Peter Kjellerstedt
2021-08-26 17:45   ` [OE-core] " Martin Jansa
2021-08-26 17:57     ` Peter Kjellerstedt [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=54cf0ace72d74dfb923843ff19baa2e4@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=martin.jansa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox