Skip to contentSkip to conversation

alsa-lib: add license info

PATCH New Danomi Manchego 5 participants 14 messages Aug 19, 2012 – Aug 27, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/8 alsa-lib: add license info

---
 package/alsa-lib/alsa-lib.mk |    2 ++
 1 file changed, 2 insertions(+)
package/alsa-lib/alsa-lib.mk +2 -0
index c3f61ff..8ed1339 100644
@@ -7,6 +7,8 @@
 ALSA_LIB_VERSION = 1.0.25
 ALSA_LIB_SOURCE = alsa-lib-$(ALSA_LIB_VERSION).tar.bz2
 ALSA_LIB_SITE = ftp://ftp.alsa-project.org/pub/lib
+ALSA_LIB_LICENSE = LGPLv2.1+
+ALSA_LIB_LICENSE_FILES = COPYING
 ALSA_LIB_INSTALL_STAGING = YES
 ALSA_LIB_CFLAGS=$(TARGET_CFLAGS)
 ALSA_LIB_CONF_OPT = --with-alsa-devdir=$(call qstrip,$(BR2_PACKAGE_ALSA_LIB_DEVDIR)) \
Signature · 1 line
1.7.9.5
#1 lore raw

PATCH 2/8 alsa-utils: add license info

---
 package/multimedia/alsa-utils/alsa-utils.mk |    2 ++
 1 file changed, 2 insertions(+)
package/multimedia/alsa-utils/alsa-utils.mk +2 -0
index 90fba51..7043837 100644
@@ -7,6 +7,8 @@
 ALSA_UTILS_VERSION = 1.0.25
 ALSA_UTILS_SOURCE = alsa-utils-$(ALSA_UTILS_VERSION).tar.bz2
 ALSA_UTILS_SITE = ftp://ftp.alsa-project.org/pub/utils
+ALSA_UTILS_LICENSE = GPLv2
+ALSA_UTILS_LICENSE_FILES = COPYING
 ALSA_UTILS_INSTALL_STAGING = YES
 ALSA_UTILS_DEPENDENCIES = alsa-lib \
 	$(if $(BR2_PACKAGE_NCURSES),ncurses)
Signature · 1 line
1.7.9.5
#2 lore raw

PATCH 3/8 faad2: add license info

In reply to Danomi Manchego
---
 package/multimedia/faad2/faad2.mk |    2 ++
 1 file changed, 2 insertions(+)
package/multimedia/faad2/faad2.mk +2 -0
index b0078f5..f3c4712 100644
@@ -6,6 +6,8 @@
 
 FAAD2_VERSION = 2.7
 FAAD2_SITE = http://$(BR2_SOURCEFORGE_MIRROR).dl.sourceforge.net/sourceforge/faac
+FAAD2_LICENSE = GPLv2
+FAAD2_LICENSE_FILES = COPYING
 # frontend/faad calls frexp()
 FAAD2_CONF_ENV = LIBS=-lm
 FAAD2_INSTALL_STAGING = YES
Signature · 1 line
1.7.9.5
#3 lore raw

PATCH 4/8 nano: add license info

In reply to Danomi Manchego
---
 package/nano/nano.mk |    2 ++
 1 file changed, 2 insertions(+)
package/nano/nano.mk +2 -0
index 164c7a6..61bf218 100644
@@ -6,6 +6,8 @@
 
 NANO_VERSION = 2.3.1
 NANO_SITE = http://www.nano-editor.org/dist/v2.3
+NANO_LICENSE = GPLv3+
+NANO_LICENSE_FILES = COPYING
 NANO_MAKE_ENV = CURSES_LIB="-lncurses"
 NANO_CONF_OPT = --without-slang
 NANO_DEPENDENCIES = ncurses
Signature · 1 line
1.7.9.5
#4 lore raw

PATCH 5/8 fbdump: add license info

In reply to Danomi Manchego
---
 package/fbdump/fbdump.mk |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
package/fbdump/fbdump.mk +2 -1
index 176d254..3ca10bf 100644
@@ -6,6 +6,7 @@
 FBDUMP_VERSION:=0.4.2
 FBDUMP_SOURCE:=fbdump-$(FBDUMP_VERSION).tar.gz
 FBDUMP_SITE:=http://www.rcdrummond.net/fbdump
+FBDUMP_LICENSE = GPLv2
+FBDUMP_LICENSE_FILES = COPYING
 
 $(eval $(autotools-package))
-
Signature · 1 line
1.7.9.5
#5 lore raw

PATCH 6/8 fontconfig: add license info

In reply to Danomi Manchego
---
 package/fontconfig/fontconfig.mk |    2 ++
 1 file changed, 2 insertions(+)
package/fontconfig/fontconfig.mk +2 -0
index 843b34f..8c30263 100644
@@ -6,6 +6,8 @@
 FONTCONFIG_VERSION = 2.6.0
 FONTCONFIG_SOURCE = fontconfig-$(FONTCONFIG_VERSION).tar.gz
 FONTCONFIG_SITE = http://fontconfig.org/release
+FONTCONFIG_LICENSE = fontconfig
+FONTCONFIG_LICENSE_FILES = COPYING
 FONTCONFIG_AUTORECONF = YES
 FONTCONFIG_INSTALL_STAGING = YES
 # This package does not like using the target cflags for some reason.
Signature · 1 line
1.7.9.5
#6 lore raw

PATCH 6/8 fontconfig: add license info

Le Sun, 19 Aug 2012 16:18:28 -0400,
Danomi Manchego <[email protected]> a ?crit :

package/fontconfig/fontconfig.mk line 10

Quoted 2 lines
package/fontconfig/fontconfig.mk +2 -0
+FONTCONFIG_LICENSE = fontconfig
+FONTCONFIG_LICENSE_FILES = COPYING

For special licenses, I thought that the convention was to use the string "foo license", and not just "foo". Luca?

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#7 lore raw

PATCH 6/8 fontconfig: add license info

Quoted 2 lines

For special licenses, I thought that the convention was to use the string "foo license", and not just "foo".

Grepping, I see only three exceptions to this:

package/zxing/zxing.mk:ZXING_LICENSE = Apache package/poco/poco.mk:POCO_LICENSE = Boost-v1.0 package/openssl/openssl.mk:OPENSSL_LICENSE = OpenSSL or SSLeay

So, I'll resubmit as "fontconfig license".

What about sqlite? According to http://www.sqlite.org/copyright.html, it is "public domain". Should sqlite's license also be "sqlite license", or "public domain"?

Danomi -

Quoted 9 lines · Thomas Petazzoni

Le Sun, 19 Aug 2012 16:18:28 -0400,
Danomi Manchego <[email protected]> a ?crit :

package/fontconfig/fontconfig.mk line 10

Quoted 2 lines
package/fontconfig/fontconfig.mk +2 -0
+FONTCONFIG_LICENSE = fontconfig
+FONTCONFIG_LICENSE_FILES = COPYING

For special licenses, I thought that the convention was to use the string "foo license", and not just "foo". Luca?

Quoted 7 lines

Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120821/04481382/attachment.html>

#8 lore raw

PATCH 6/8 fontconfig: add license info

Hi Danomi,

Quoted 7 lines · Danomi Manchego
Quoted 2 lines

For special licenses, I thought that the convention was to use the string "foo license", and not just "foo".

Grepping, I see only three exceptions to this:

package/zxing/zxing.mk:ZXING_LICENSE = Apache
package/poco/poco.mk:POCO_LICENSE = Boost-v1.0

Apache and Boost refer (also) to specific software licenses. See
http://www.apache.org/licenses/ and http://www.boost.org/users/license.html. I think we should add a version number to Apache license info, though. In the case of zxing it's v2.0.

baruch

Quoted 27 lines

package/openssl/openssl.mk:OPENSSL_LICENSE = OpenSSL or SSLeay

So, I'll resubmit as "fontconfig license".

What about sqlite? According to http://www.sqlite.org/copyright.html, it is "public domain". Should sqlite's license also be "sqlite license", or "public domain"?

Danomi -

Quoted 15 lines · Thomas Petazzoni

Le Sun, 19 Aug 2012 16:18:28 -0400,
Danomi Manchego <[email protected]> a ?crit :

package/fontconfig/fontconfig.mk line 10

Quoted 2 lines
package/fontconfig/fontconfig.mk +2 -0
+FONTCONFIG_LICENSE = fontconfig
+FONTCONFIG_LICENSE_FILES = COPYING

For special licenses, I thought that the convention was to use the string "foo license", and not just "foo". Luca?

Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

Signature · 3 lines
     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 -
#9 lore raw

PATCH 6/8 fontconfig: add license info

In reply to Danomi Manchego
Quoted 2 lines · Danomi Manchego

What about sqlite? According to http://www.sqlite.org/copyright.html, it is "public domain". Should sqlite's license also be "sqlite license", or "public domain"?

I'd use 'Public domain', it's a very specific and well-known legal term. It
means the authors forfeit their copyright, and there are no restrictions whatsoever on the use of the software.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#10 lore raw

PATCH 6/8 fontconfig: add license info

Quoted 11 lines · Arnout Vandecappelle
Quoted 4 lines · Danomi Manchego

What about sqlite? According to
http://www.sqlite.org/copyright.html, it is "public domain". Should sqlite's license
also be "sqlite license", or "public domain"?

I'd use 'Public domain', it's a very specific and well-known legal
term. It
means the authors forfeit their copyright, and there are no restrictions whatsoever
on the use of the software.

I agree with Arnout. "public domain" is much more informative, and is not ambiguous.

Luca

#11 lore raw

PATCH 7/8 rsync: add license info

In reply to Danomi Manchego
---
 package/rsync/rsync.mk |    2 ++
 1 file changed, 2 insertions(+)
package/rsync/rsync.mk +2 -0
index f2df256..3963547 100644
@@ -7,6 +7,8 @@
 RSYNC_VERSION = 3.0.9
 RSYNC_SOURCE = rsync-$(RSYNC_VERSION).tar.gz
 RSYNC_SITE = http://rsync.samba.org/ftp/rsync/src
+RSYNC_LICENSE = GPLv3+
+RSYNC_LICENSE_FILES = COPYING
 RSYNC_CONF_OPT = $(if $(BR2_ENABLE_DEBUG),--enable-debug,--disable-debug)
 RSYNC_CONF_OPT = --with-included-popt
 
Signature · 1 line
1.7.9.5
#12 lore raw

PATCH 8/8 librsync: add license info

In reply to Danomi Manchego
---
 package/librsync/librsync.mk |    2 ++
 1 file changed, 2 insertions(+)
package/librsync/librsync.mk +2 -0
index 864297b..f0f543f 100644
@@ -6,6 +6,8 @@
 LIBRSYNC_VERSION:=0.9.7
 LIBRSYNC_SOURCE:=librsync-$(LIBRSYNC_VERSION).tar.gz
 LIBRSYNC_SITE:=http://$(BR2_SOURCEFORGE_MIRROR).dl.sourceforge.net/sourceforge/librsync/
+LIBRSYNC_LICENSE = LGPLv2.1+
+LIBRSYNC_LICENSE_FILES = COPYING
 LIBRSYNC_INSTALL_STAGING = YES
 LIBRSYNC_DEPENDENCIES = zlib bzip2 popt
 
Signature · 1 line
1.7.9.5
#13 lore raw

PATCH 1/8 alsa-lib: add license info

In reply to Danomi Manchego

Le Sun, 19 Aug 2012 16:18:23 -0400,
Danomi Manchego <[email protected]> a ?crit :

Quoted 1 line

Thanks. I have applied all patches except patch 6/8 on fontconfig, due to the specific comment I sent on it.

Thanks!

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com