From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] protobuf: add license information
Date: Tue, 31 Jul 2012 11:30:54 +0300 [thread overview]
Message-ID: <20120731083054.GC9675@sapphire.tkos.co.il> (raw)
In-Reply-To: <1343722559-10028-1-git-send-email-spdawson@gmail.com>
Hi Simon,
On Tue, Jul 31, 2012 at 09:15:59AM +0100, spdawson at gmail.com wrote:
> From: Simon Dawson <spdawson@gmail.com>
>
> Signed-off-by: Simon Dawson <spdawson@gmail.com>
> ---
> package/protobuf/protobuf.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/protobuf/protobuf.mk b/package/protobuf/protobuf.mk
> index 6e49dd3..653e90e 100644
> --- a/package/protobuf/protobuf.mk
> +++ b/package/protobuf/protobuf.mk
> @@ -6,6 +6,8 @@
> PROTOBUF_VERSION = 2.4.1
> PROTOBUF_SOURCE = protobuf-$(PROTOBUF_VERSION).tar.gz
> PROTOBUF_SITE = http://protobuf.googlecode.com/files/
> +PROTOBUF_LICENSE = PROPRIETARY
The text at https://code.google.com/p/protobuf/source/browse/trunk/COPYING.txt
looks more like a 3-clause BSD licence (see
http://en.wikipedia.org/wiki/BSD_licenses). Is this considered proprietary?
baruch
> +PROTOBUF_LICENSE_FILES = COPYING.txt
>
> # N.B. Need to use host protoc during cross compilation.
> PROTOBUF_DEPENDENCIES = host-protobuf
> --
> 1.7.9.5
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-07-31 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 8:15 [Buildroot] [PATCH] protobuf: add license information spdawson at gmail.com
2012-07-31 8:30 ` Baruch Siach [this message]
2012-07-31 8:36 ` Simon Dawson
2012-07-31 8:38 ` Luca Ceresoli
2012-07-31 8:42 ` Simon Dawson
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=20120731083054.GC9675@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--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