Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] breakpad: Upgrade to latest
Date: Tue, 22 Nov 2016 17:54:12 +0100	[thread overview]
Message-ID: <20161122165412.GD3348@jama> (raw)
In-Reply-To: <20161109020926.14361-1-raj.khem@gmail.com>

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

On Tue, Nov 08, 2016 at 06:09:26PM -0800, Khem Raj wrote:
> Switch to using git
> Gets aarch64 support
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  .../breakpad/{breakpad_svn.bb => breakpad_git.bb}      | 18 +++++++++++++++---
>  1 file changed, 15 insertions(+), 3 deletions(-)
>  rename meta-oe/recipes-devtools/breakpad/{breakpad_svn.bb => breakpad_git.bb} (87%)
> 
> diff --git a/meta-oe/recipes-devtools/breakpad/breakpad_svn.bb b/meta-oe/recipes-devtools/breakpad/breakpad_git.bb
> similarity index 87%
> rename from meta-oe/recipes-devtools/breakpad/breakpad_svn.bb
> rename to meta-oe/recipes-devtools/breakpad/breakpad_git.bb
> index b573ea5..6dc6500 100644
> --- a/meta-oe/recipes-devtools/breakpad/breakpad_svn.bb
> +++ b/meta-oe/recipes-devtools/breakpad/breakpad_git.bb
> @@ -13,9 +13,21 @@ inherit autotools
>  
>  BBCLASSEXTEND = "native"
>  
> -SRCREV = "r1435"
> -SRC_URI = "svn://google-breakpad.googlecode.com/svn;module=trunk;protocol=http"
> -S = "${WORKDIR}/trunk"

Please define some sane PV, now it goes backwards:
breakpad-git: Package version for package breakpad-dbg went backwards
which would break package feeds from (0:svn-r0.36 to 0:git-r0.0)
[version-going-backwards]

> +SRCREV_breakpad = "2f6cb866d615d6240a18c7535c994c6bb93b1ba5"
> +SRCREV_glog = "d8cb47f77d1c31779f3ff890e1a5748483778d6a"
> +SRCREV_gmock = "f7d03d2734759ee12b57d2dbcb695607d89e8e05"
> +SRCREV_gtest = "ec44c6c1675c25b9827aacd08c02433cccde7780"
> +SRCREV_protobuf = "cb6dd4ef5f82e41e06179dcd57d3b1d9246ad6ac"
> +SRCREV_lss = "1549d20f6d3e7d66bb4e687c0ab9da42c2bff2ac"
> +
> +SRC_URI = "git://github.com/google/breakpad;name=breakpad \
> +           git://github.com/google/glog.git;destsuffix=git/src/third_party/glog;name=glog \
> +           git://github.com/google/googlemock.git;destsuffix=git/src/testing;name=gmock \
> +           git://github.com/google/googletest.git;destsuffix=git/src/testing/gtest;name=gtest \
> +           git://github.com/google/protobuf.git;destsuffix=git/src/third_party/protobuf/protobuf;name=protobuf \
> +           git://chromium.googlesource.com/linux-syscall-support;protocol=https;destsuffix=git/src/third_party/lss;name=lss \
> +"
> +S = "${WORKDIR}/git"
>  
>  COMPATIBLE_MACHINE_powerpc = "(!.*ppc).*"
>  
> -- 
> 2.10.2
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

      reply	other threads:[~2016-11-22 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  2:09 [meta-oe][PATCH] breakpad: Upgrade to latest Khem Raj
2016-11-22 16:54 ` Martin Jansa [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=20161122165412.GD3348@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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