From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/6] libuci: update legal info
Date: Mon, 4 Jul 2016 17:46:26 +0200 [thread overview]
Message-ID: <20160704154626.GC3549@free.fr> (raw)
In-Reply-To: <1467636386-6759-2-git-send-email-rahul.bedarkar@imgtec.com>
Rahul, All,
On 2016-07-04 18:16 +0530, Rahul Bedarkar spake thusly:
> CLI tool and lua bindings are released under GPLv2.
>
> Reviewed-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
> ---
> package/libuci/libuci.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/libuci/libuci.mk b/package/libuci/libuci.mk
> index 8c060d5..b9bd0c7 100644
> --- a/package/libuci/libuci.mk
> +++ b/package/libuci/libuci.mk
> @@ -6,7 +6,7 @@
>
> LIBUCI_VERSION = e339407372ffc70b1451e4eda218c01aa95a6a7f
> LIBUCI_SITE = git://nbd.name/uci.git
> -LIBUCI_LICENSE = LGPLv2.1
> +LIBUCI_LICENSE = LGPLv2.1, GPLv2 (tools)
> LIBUCI_INSTALL_STAGING = YES
> LIBUCI_DEPENDENCIES = libubox
>
> @@ -15,6 +15,7 @@ LIBUCI_DEPENDENCIES += lua
> LIBUCI_CONF_OPTS += -DBUILD_LUA=ON \
> -DLUAPATH=/usr/lib/lua/5.1 \
> -DLUA_CFLAGS=-I$(STAGING_DIR)/usr/include
> +LIBUCI_LICENSE += , GPLv2 (lua bindings)
Although this is correct, this causes the resulting string to be
ill-formatted:
LGPLv2.1, GPLv2 (tools) , GPLv2 (lua bindings)
In this case, what we did in other such conditions, was:
LIBUCI_LICENSE = LGPLv2.1, GPLv2 (tools)
ifeq ($(BR2_PACKAGE_LUA_5_1),y)
LIBUCI_LICENSE := $(LIBUCI_LICENSE), GPLv2 (lua bindings)
endif
See for example qt or freeswitch.
Regards,
Yann E. MORIN.
> else
> LIBUCI_CONF_OPTS += -DBUILD_LUA=OFF
> endif
> --
> 2.6.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-07-04 15:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 12:46 [Buildroot] [PATCH 1/6] gnutls: update legal info Rahul Bedarkar
2016-07-04 12:46 ` [Buildroot] [PATCH 2/6] libuci: " Rahul Bedarkar
2016-07-04 15:46 ` Yann E. MORIN [this message]
2016-07-04 12:46 ` [Buildroot] [PATCH 3/6] dbus: " Rahul Bedarkar
2016-07-04 12:46 ` [Buildroot] [PATCH 4/6] iw: correct license name Rahul Bedarkar
2016-07-04 15:56 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 5/6] gmp: correct legal info Rahul Bedarkar
2016-07-04 16:07 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 6/6] alsa-lib: update " Rahul Bedarkar
2016-07-04 16:14 ` Yann E. MORIN
2016-07-05 7:15 ` Thomas Petazzoni
2016-07-04 15:39 ` [Buildroot] [PATCH 1/6] gnutls: " Yann E. MORIN
2016-07-04 22:13 ` Thomas Petazzoni
2016-07-04 22:14 ` 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=20160704154626.GC3549@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