All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH v3 1/2] gflags: New recipe
Date: Fri, 12 Aug 2016 08:37:21 +0200	[thread overview]
Message-ID: <CAPybu_35+Ug0CpasvpVg=WfC2N3F_6hmcSbN7CJ7tquhGr7C8A@mail.gmail.com> (raw)
In-Reply-To: <D01FFBA5-7B48-4F0F-B1E0-3D96FE48044F@gmail.com>

Hi Khem

On Fri, Aug 12, 2016 at 7:36 AM, Khem Raj <raj.khem@gmail.com> wrote:

>> +DESCRIPTION = "The gflags package contains a C++ library that implements commandline flags processing. It includes built-in support for standard types such as string and the ability to define flags in the source file in which they are used"
>> +HOMEPAGE = "https://github.com/gflags/gflags"
>> +LICENSE = “BSD"
>
> which Clause ?

I have no idea,
I has the same License file as glog:

https://github.com/gflags/gflags/blob/master/COPYING.txt
https://github.com/google/glog/blob/master/COPYING

That is why I choose BSD.

Regards!


  reply	other threads:[~2016-08-12  6:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 13:07 [meta-oe][PATCH v3 1/2] gflags: New recipe Ricardo Ribalda Delgado
2016-08-11 13:07 ` [meta-oe][PATCH v3 2/2] glog: Update to version 0.3.4 Ricardo Ribalda Delgado
2016-08-11 13:33 ` [meta-oe][PATCH v3 1/2] gflags: New recipe Jack Mitchell
2016-08-12  5:36 ` Khem Raj
2016-08-12  6:37   ` Ricardo Ribalda Delgado [this message]
2016-08-12  7:26     ` Khem Raj
2016-08-12  8:06       ` Ricardo Ribalda Delgado
2016-08-12  8:56         ` Martin Jansa

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='CAPybu_35+Ug0CpasvpVg=WfC2N3F_6hmcSbN7CJ7tquhGr7C8A@mail.gmail.com' \
    --to=ricardo.ribalda@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.