From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] metadata_scm.bbclass: Do not assume ${COREBASE} is a Git repo
Date: Thu, 28 Apr 2016 14:34:05 +0000 [thread overview]
Message-ID: <fe76014a152542ac8ef2113f0406524d@XBOX02.axis.com> (raw)
In-Reply-To: <CABcZANmw0D1xZsFQZYYxyQDwbj3P_8Ab1CO0k52f2XpKbUUwFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
Yes, it was intentional. I mentioned this in the cover letter. I can of course add something about it to the commit message as well if you like.
//Peter
From: kergoth@gmail.com [mailto:kergoth@gmail.com] On Behalf Of Christopher Larson
Sent: den 27 april 2016 22:27
To: Peter Kjellerstedt
Cc: Patches and discussions about the oe-core layer
Subject: Re: [OE-core] [PATCH 1/1] metadata_scm.bbclass: Do not assume ${COREBASE} is a Git repo
On Tue, Apr 26, 2016 at 12:49 PM, Peter Kjellerstedt <peter.kjellerstedt@axis.com<mailto:peter.kjellerstedt@axis.com>> wrote:
The functions base_detect_revision() and base_detect_branch() try to
extract SCM meta information from the path returned by
base_get_scmbasepath(), which currently returns ${COREBASE}. However,
making the assumption that ${COREBASE} contains SCM meta information
can be false. It is true for Poky, but not necessarily other
environments. A better option is to look for the SCM meta information
based on the meta layer.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com<mailto:peter.kjellerstedt@axis.com>>
---
meta/classes/metadata_scm.bbclass | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/classes/metadata_scm.bbclass b/meta/classes/metadata_scm.bbclass
index 0f7f423..2e6fac2 100644
--- a/meta/classes/metadata_scm.bbclass
+++ b/meta/classes/metadata_scm.bbclass
@@ -4,8 +4,7 @@ METADATA_REVISION ?= "${@base_detect_revision(d)}"
def base_detect_revision(d):
path = base_get_scmbasepath(d)
- scms = [base_get_metadata_git_revision, \
- base_get_metadata_svn_revision]
+ scms = [base_get_metadata_git_revision]
Was this change intended? Because it doesn't match up with the commit message, as far as I can see.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
[-- Attachment #2: Type: text/html, Size: 5487 bytes --]
next prev parent reply other threads:[~2016-04-28 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 19:49 [PATCH 0/1] Improve how to determine METADATA_REVISION Peter Kjellerstedt
2016-04-26 19:49 ` [PATCH 1/1] metadata_scm.bbclass: Do not assume ${COREBASE} is a Git repo Peter Kjellerstedt
2016-04-27 20:26 ` Christopher Larson
2016-04-28 14:34 ` Peter Kjellerstedt [this message]
2016-04-28 16:11 ` Christopher Larson
2016-04-29 17:04 ` Peter Kjellerstedt
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=fe76014a152542ac8ef2113f0406524d@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=clarson@kergoth.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