radvd: bump to version 1.10.0
PATCH 1/2 radvd: bump to version 1.10.0
Adds 6LoWPAN support.
--- package/radvd/radvd.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
package/radvd/radvd.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -RADVD_VERSION = 1.9.9 +RADVD_VERSION = 1.10.0 RADVD_SOURCE = radvd-$(RADVD_VERSION).tar.xz RADVD_SITE = http://www.litech.org/radvd/dist RADVD_DEPENDENCIES = host-bison flex libdaemon host-flex host-pkgconf
Signature · 1 line
1.8.3.2
PATCH 2/2 libcgicc: bump to version 3.2.13
Also add license files and docs license definition.
--- package/libcgicc/libcgicc.mk | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
package/libcgicc/libcgicc.mk +3 -2
@@ -4,10 +4,11 @@ # ################################################################################ -LIBCGICC_VERSION = 3.2.12 +LIBCGICC_VERSION = 3.2.13 LIBCGICC_SITE = $(BR2_GNU_MIRROR)/cgicc LIBCGICC_SOURCE = cgicc-$(LIBCGICC_VERSION).tar.gz -LIBCGICC_LICENSE = LGPLv3+ +LIBCGICC_LICENSE = LGPLv3+, docs: GFDL1.2+ +LIBCGICC_LICENSE_FILES = COPYING.LIB COPYING.DOC LIBCGICC_INSTALL_STAGING = YES LIBCGICC_AUTORECONF = YES LIBCGICC_CONFIG_SCRIPTS = cgicc-config
Signature · 1 line
1.8.3.2
Thomas Petazzoni
AppliedPATCH 2/2 libcgicc: bump to version 3.2.13
Dear Gustavo Zacarias,
Quoted 6 lines · Gustavo Zacarias
Also add license files and docs license definition.
Signed-off-by Gustavo Zacarias <[email protected]>--- package/libcgicc/libcgicc.mk | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
Applied, thanks, with one minor change.
Quoted 1 line
+LIBCGICC_LICENSE = LGPLv3+, docs: GFDL1.2+
I've changed this to the more traditional:
LGPLv3+ (library), GFDL1.2+ (docs)
Though I'm wondering if:
* We shouldn't use GFDLv1.2+ instead, like we do for GPL/LGPL.
* Whether we should really worry about the documentation license, since we don't allow the installation of the documentation on the target. I don't think we have any other package that describe the license of their documentation.
Cc'ing Luca and Yann to get an opinion on this.
Thanks,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 2/2 libcgicc: bump to version 3.2.13
Quoted 6 lines · Thomas Petazzoni
I've changed this to the more traditional:
LGPLv3+ (library), GFDL1.2+ (docs)Though I'm wondering if:
Quoted 8 lines
* We shouldn't use GFDLv1.2+ instead, like we do for GPL/LGPL.
* Whether we should really worry about the documentation license, since we don't allow the installation of the documentation on the target. I don't think we have any other package that describe the license of their documentation.
Cc'ing Luca and Yann to get an opinion on this.
At this point we nuke docs so +1 from me, i added it because i saw COPYING.* included it and there was one other package that mentions the FDL (valgrind).
But yeah, it won't be in staging or target any time soon so +1 about the second point.
Regards.
PATCH 2/2 libcgicc: bump to version 3.2.13
Dear Gustavo Zacarias,
Quoted 5 lines · Gustavo Zacarias
At this point we nuke docs so +1 from me, i added it because i saw COPYING.* included it and there was one other package that mentions the FDL (valgrind).
But yeah, it won't be in staging or target any time soon so +1 about the second point.
So you can send a patch that removes it? :-)
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 2/2 libcgicc: bump to version 3.2.13
In reply to Thomas PetazzoniThomas, All,
On 2014-03-30 11:30 +0200, Thomas Petazzoni spake thusly:
Quoted 12 lines · Gustavo Zacarias
Quoted 6 lines
Also add license files and docs license definition.
Signed-off-by Gustavo Zacarias <[email protected]>--- package/libcgicc/libcgicc.mk | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)Applied, thanks, with one minor change.
Quoted 1 line
+LIBCGICC_LICENSE = LGPLv3+, docs: GFDL1.2+
Quoted 7 lines
I've changed this to the more traditional:
LGPLv3+ (library), GFDL1.2+ (docs)Though I'm wondering if:
* We shouldn't use GFDLv1.2+ instead, like we do for GPL/LGPL.
For the sake of consistency, yes.i
For the records, however, SPDX does not list any 'or-later' for the GFDL:
http://spdx.org/licenses/
---
GNU Free Documentation License v1.1 GFDL-1.1
GNU Free Documentation License v1.2 GFDL-1.2
GNU Free Documentation License v1.3 GFDL-1.3
GNU General Public License v1.0 only GPL-1.0
GNU General Public License v1.0 or later GPL-1.0+
GNU General Public License v2.0 only GPL-2.0
GNU General Public License v2.0 or later GPL-2.0+
---
But that is valid for an author to specify this 'or later', so OK for the 'GFDLv1.2+'
Quoted 4 lines
* Whether we should really worry about the documentation license, since we don't allow the installation of the documentation on the target. I don't think we have any other package that describe the license of their documentation.
Well, if we're sure there's no installed doc, then we do not need this in the licensing info. But if in doubt, better let the user check on his side if the license indeed applies or not.
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | 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. | '------------------------------^-------^------------------^--------------------'
PATCH 2/2 libcgicc: bump to version 3.2.13
In reply to Thomas PetazzoniHi Thomas,
Quoted 14 lines · Thomas Petazzoni
Dear Gustavo Zacarias,
Quoted 6 lines · Gustavo Zacarias
Also add license files and docs license definition.
Signed-off-by Gustavo Zacarias <[email protected]>--- package/libcgicc/libcgicc.mk | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)Applied, thanks, with one minor change.
Quoted 1 line
+LIBCGICC_LICENSE = LGPLv3+, docs: GFDL1.2+
Quoted 7 lines
I've changed this to the more traditional:
LGPLv3+ (library), GFDL1.2+ (docs)Though I'm wondering if:
* We shouldn't use GFDLv1.2+ instead, like we do for GPL/LGPL.
Unless there is a good reason, we should the same style for all licenses.
So, yes, we should use GFDLv1.2+.
Or... We may sync with SPDX: GPL-3.0, LGPL-2.1+, BSD-3-Clause, etc.
Quoted 5 lines
* Whether we should really worry about the documentation license, since we don't allow the installation of the documentation on the target. I don't think we have any other package that describe the license of their documentation.
I'm quite neutral on this point, but I would like at least a comment to make it clear that whoever added the license info has checked, not just missed the other license(s).
Example:
# The docs are GFDLv1.2+, but not installed
LIBFOO_LICENSE = LGPLv3+
Signature · 1 line
Luca
Thomas Petazzoni
AppliedPATCH 1/2 radvd: bump to version 1.10.0
In reply to Gustavo ZacariasDear Gustavo Zacarias,
Quoted 6 lines · Gustavo Zacarias
Adds 6LoWPAN support.
Signed-off-by Gustavo Zacarias <[email protected]>--- package/radvd/radvd.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com