From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] libftdi: Change to use GPLv2 intead of GPLv2-REL
Date: Tue, 09 Oct 2012 16:17:43 +0200 [thread overview]
Message-ID: <k51bm2$h7r$1@ger.gmane.org> (raw)
In-Reply-To: <1349784265-25901-1-git-send-email-mertsas@cisco.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 09-10-12 14:04, Martin Ertsaas schreef:
> 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.
>
> Signed-off-by: Martin Ertsaas <mertsas@cisco.com> ---
> meta-oe/recipes-support/libftdi/libftdi_0.19.bb | 2 +- 1 files
> changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta-oe/recipes-support/libftdi/libftdi_0.19.bb
> 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"
>
> -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-----
next prev parent reply other threads:[~2012-10-09 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 12:04 [meta-oe][PATCH] libftdi: Change to use GPLv2 intead of GPLv2-REL Martin Ertsaas
2012-10-09 14:17 ` Koen Kooi [this message]
2012-10-09 17:27 ` Martin Jansa
2012-10-10 5:50 ` Martin Ertsås
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='k51bm2$h7r$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/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