Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/4] gtest, gmock: Move download link away from Google Code
Date: Fri, 1 Jul 2016 17:19:17 +0200	[thread overview]
Message-ID: <20160701151917.GB17666@free.fr> (raw)
In-Reply-To: <1537894575.7432607.1467369780476.JavaMail.zimbra@datacom.ind.br>

Carlos, All,

On 2016-07-01 07:43 -0300, Carlos Santos spake thusly:
> > On 2016-02-22 09:23 -0300, Carlos Santos spake thusly:
> >> Google Code is being shut down. The google code site which hosts the
> >> source .zip for gtest and gmock references github.com/google/googletest,
> >> now.
> >> 
> >> Change the GTEST_SITE and GMOCK_SITE to this new github repo, fix the
> >> version, fix the paths, and remove the custom extraction commands.
[--SNIP--]
> > As I understand it, gtest and gmock are being phased out as separate
> > packages, and are to be replaced with the googletest package.
> > 
> > So why don't we directly add "googletest" and get rid of gtest and
> > gmock, rather than fix them to eventually get rid of them?
> 
> Because we (DATACOM) have have a hundred packages in our BR2_EXTERNAL
> that depend on GMock and GTest as separate packages. It will take some
> time migrate them.

OK, but since gtest and gmock ar estill available from gcode, we can keep
them as-is for now, especially since changing their location require
that we get some invasive changes.

> > I've marked this patch as rejected in our patchwork now, while waiting
> > for the patches that add googletest and then removes gtest/gmock as
> > separate packages.
> 
> OK, I will keep it as a local change while working on the new package.

OK, thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-07-01 15:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <444859483-2268-1-git-send-email-alan@softiron.co.uk>
2016-02-22 12:23 ` [Buildroot] [PATCH v2 0/4] Move download links away from Google Code Carlos Santos
2016-02-22 12:23   ` [Buildroot] [PATCH v2 1/4] dsp-tools: Move download link " Carlos Santos
2016-02-22 12:23   ` [Buildroot] [PATCH v2 2/4] gst-dsp: " Carlos Santos
2016-02-22 12:23   ` [Buildroot] [PATCH v2 3/4] gst-omapfb: " Carlos Santos
2016-02-22 12:23   ` [Buildroot] [PATCH v2 4/4] gtest, gmock: " Carlos Santos
2016-07-01  9:49     ` Yann E. MORIN
2016-07-01 10:43       ` Carlos Santos
2016-07-01 15:19         ` Yann E. MORIN [this message]
2016-02-25 21:41   ` [Buildroot] [PATCH v2 0/4] Move download links " Thomas Petazzoni
2016-02-26 11:43     ` Carlos Santos
2016-02-27 14:42       ` Thomas Petazzoni

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=20160701151917.GB17666@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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