From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] espeak: new package
Date: Mon, 14 Oct 2013 19:58:35 +0200 [thread overview]
Message-ID: <20131014195835.4e87ee20@skate> (raw)
In-Reply-To: <CACjG4BJKxk6=y7iAyBxsw3E5HA=x4kxM+GWXCqbn8Z4Tx6XH-A@mail.gmail.com>
Dear arnaud aujon,
On Mon, 14 Oct 2013 19:49:09 +0200, arnaud aujon wrote:
> I will send a new patch shortly.
> About the licence, the file Licence.txt say GPLv3 but you're right in the
> source code we can find GPLv3+, what do you do in this case ?
It's very often the case: the COPYING or License file provides the
license text for a given version of the GPL license, and the code
itself precises whether it's only this version, or this version or
later. And since the FSF recommends using the "or later" wording, many
projects do this.
In this case, the <pkg>_LICENSE should really be GPLv3+, because that's
what the source code says.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-14 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 17:15 [Buildroot] [PATCH v5] espeak: new package Arnaud Aujon
2013-10-14 17:19 ` Ryan Barnett
2013-10-14 17:40 ` Thomas Petazzoni
2013-10-14 17:49 ` arnaud aujon
2013-10-14 17:58 ` Thomas Petazzoni [this message]
2013-10-14 18:07 ` arnaud aujon
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=20131014195835.4e87ee20@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox