Skip to contentSkip to conversation

libftdi: Change to use GPLv2 intead of GPLv2-REL

PATCH Superseded Martin Ertsaas 3 participants 4 messages Oct 9, 2012 – Oct 10, 2012

v1 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libftdi: Change to use GPLv2 intead of GPLv2-REL

According to http://www.intra2net.com/en/developer/libftdi/, libftdi itself is licensed under LGPLv2, with some parts (eeprom programmer) is licensed under GPLv2. There doesn't seem to be any part licensed under a GPLv2-REL variation of GPLv2, and so we should use GPLv2 instead of GPLv2-REL.

---
 meta-oe/recipes-support/libftdi/libftdi_0.19.bb |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta-oe/recipes-support/libftdi/libftdi_0.19.bb +1 -1
index 2dba3f4..0842aaf 100644
@@ -4,7 +4,7 @@ including the popular bitbang mode."
 HOMEPAGE = "http://www.intra2net.com/en/developer/libftdi/"
 SECTION = "libs"
 
-LICENSE = "LGPLv2.1 GPLv2-RLE"
+LICENSE = "LGPLv2.1 GPLv2"
 LIC_FILES_CHKSUM= "file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe \
                    file://COPYING.LIB;md5=db979804f025cf55aabec7129cb671ed \
                   "
Signature · 1 line
1.7.8.6
#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 09-10-12 14:04, Martin Ertsaas schreef:

Quoted 17 lines

According to http://www.intra2net.com/en/developer/libftdi/, libftdi itself is licensed under LGPLv2, with some parts (eeprom programmer) is licensed under GPLv2. There doesn't seem to be any part licensed under a GPLv2-REL variation of GPLv2, and so we should use GPLv2 instead of GPLv2-REL.

meta-oe/recipes-support/libftdi/libftdi_0.19.bb | 2 +- 1 files
changed, 1 insertions(+), 1 deletions(-)

(quoted diff) +0 -0

b/meta-oe/recipes-support/libftdi/libftdi_0.19.bb index 2dba3f4..0842aaf 100644 --- a/meta-oe/recipes-support/libftdi/libftdi_0.19.bb +++ b/meta-oe/recipes-support/libftdi/libftdi_0.19.bb @@ -4,7 +4,7 @@ including the popular bitbang mode." HOMEPAGE = "http://www.intra2net.com/en/developer/libftdi/" SECTION = "libs"

Quoted 4 lines

-LICENSE = "LGPLv2.1 GPLv2-RLE" +LICENSE = "LGPLv2.1 GPLv2" LIC_FILES_CHKSUM= "file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe \
file://COPYING.LIB;md5=db979804f025cf55aabec7129cb671ed \ "

Since LICENSE ends up in the package: missing PR bump.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQdDIGMkyGM64RGpERAlaLAKCCNbr1Tcydi+Re/9Wdoc/zKVibKwCgi2bH MOFVynH6iiHafgC1/70Fq/M=
=PGD4
-----END PGP SIGNATURE-----

#2 lore raw
In reply to Martin Ertsaas
Quoted 3 lines · Martin Ertsaas

According to http://www.intra2net.com/en/developer/libftdi/, libftdi itself is licensed under LGPLv2, with some parts (eeprom programmer) is licensed under GPLv2. There doesn't seem to be any part licensed under a GPLv2-REL variation of GPLv2, and so we should use GPLv2 instead of GPLv2-REL.

Is it REL or RLE? Your subject and body says REL while LICENSE says RLE.

Cheers,

Quoted 26 lines
---
 meta-oe/recipes-support/libftdi/libftdi_0.19.bb |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta-oe/recipes-support/libftdi/libftdi_0.19.bb +1 -1
index 2dba3f4..0842aaf 100644
@@ -4,7 +4,7 @@ including the popular bitbang mode."
 HOMEPAGE = "http://www.intra2net.com/en/developer/libftdi/"
 SECTION = "libs"
 
-LICENSE = "LGPLv2.1 GPLv2-RLE"
+LICENSE = "LGPLv2.1 GPLv2"
 LIC_FILES_CHKSUM= "file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe \
                    file://COPYING.LIB;md5=db979804f025cf55aabec7129cb671ed \
                   "
Signature · 7 lines
1.7.8.6


_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#3 lore raw
Quoted 7 lines · Martin Jansa
Quoted 3 lines · Martin Ertsaas

According to http://www.intra2net.com/en/developer/libftdi/, libftdi itself is licensed under LGPLv2, with some parts (eeprom programmer) is licensed under GPLv2. There doesn't seem to be any part licensed under a GPLv2-REL variation of GPLv2, and so we should use GPLv2 instead of GPLv2-REL.

Is it REL or RLE? Your subject and body says REL while LICENSE says RLE.

Cheers,

Damn, didn't see that typo. I'll push a new one asap.

- Martin

Quoted 33 lines
Quoted 27 lines
---
 meta-oe/recipes-support/libftdi/libftdi_0.19.bb |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
meta-oe/recipes-support/libftdi/libftdi_0.19.bb +1 -1
index 2dba3f4..0842aaf 100644
@@ -4,7 +4,7 @@ including the popular bitbang mode."
 HOMEPAGE = "http://www.intra2net.com/en/developer/libftdi/"
 SECTION = "libs"
 
-LICENSE = "LGPLv2.1 GPLv2-RLE"
+LICENSE = "LGPLv2.1 GPLv2"
 LIC_FILES_CHKSUM= "file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe \
                    file://COPYING.LIB;md5=db979804f025cf55aabec7129cb671ed \
                   "
Signature · 7 lines
1.7.8.6


_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel