From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libubox: new package
Date: Tue, 4 Mar 2014 00:24:57 +0100 [thread overview]
Message-ID: <20140303232457.GC14940@free.fr> (raw)
In-Reply-To: <1391080311-30640-1-git-send-email-yegorslists@googlemail.com>
Yegor, All,
Thanks for your contribution! Some comments below...
On 2014-01-30 12:11 +0100, yegorslists at googlemail.com spake thusly:
[--SNIP--]
> diff --git a/package/libubox/Config.in b/package/libubox/Config.in
> new file mode 100644
> index 0000000..c6efb33
> --- /dev/null
> +++ b/package/libubox/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_LIBUBOX
> + bool "libubox"
> + help
> + Small utility library for OpenWrt.
In what way would this be of interest to Buildroot?
Since this is "for OpenWRT", I fail to see the relevance to Buildroot.
> + http://nbd.name/gitweb.cgi?p=luci2/libubox.git;a=summary
> diff --git a/package/libubox/libubox.mk b/package/libubox/libubox.mk
> new file mode 100644
> index 0000000..ec8fbdb
> --- /dev/null
> +++ b/package/libubox/libubox.mk
> @@ -0,0 +1,13 @@
> +################################################################################
> +#
> +# libubox
> +#
> +################################################################################
> +
> +LIBUBOX_VERSION = bbd846ec2d72b2629758b69dc122ac0b0f2c3e4b
> +LIBUBOX_SITE = git://nbd.name/luci2/libubox.git
> +LIBUBOX_LICENSE = LGPLv2.1
This is not correct:
- most of the files have a license header that do not reference the
LGPLv2.1, but which I did not recognise [0]
- some have a BSD-3c license: avl.c
- at least one file is GPLv2: md5.c
[0]
* Copyright (C) 2012 Felix Fietkau <nbd@openwrt.org>
*
* Permission to use, copy, modify, and/or distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
* WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
* MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
* ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> +LIBUBOX_INSTALL_STAGING = YES
> +LIBUBOX_CONF_OPT = -DBUILD_LUA:BOOL=OFF
Maybe that could be made conditional on whether lua is enabled or not?
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-03-03 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 11:11 [Buildroot] [PATCH] libubox: new package yegorslists at googlemail.com
2014-03-03 23:24 ` Yann E. MORIN [this message]
2014-03-04 6:59 ` Yegor Yefremov
2014-03-04 18:32 ` Yann E. MORIN
2014-03-04 19:24 ` Yegor Yefremov
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=20140303232457.GC14940@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 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.