From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] stress: add license information
Date: Tue, 8 Oct 2013 09:15:46 +0200 [thread overview]
Message-ID: <20131008091546.69d58892@skate> (raw)
In-Reply-To: <1381200417.18302.3.camel@phoenix>
Dear Axel Lin,
On Tue, 08 Oct 2013 10:46:57 +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> package/stress/stress.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/stress/stress.mk b/package/stress/stress.mk
> index 6e82b50..387166d 100644
> --- a/package/stress/stress.mk
> +++ b/package/stress/stress.mk
> @@ -6,6 +6,8 @@
>
> STRESS_VERSION = 1.0.4
> STRESS_SITE = http://people.seas.harvard.edu/~apw/stress
> +STRESS_LICENSE = GPLv3+
> +STRESS_LICENSE_FILES = COPYING
Hum, the situation is a bit weird:
* The homepage of the project states " It is written in C, and is free
software licensed under the GPLv2."
* The tarball contains a COPYING file which is a copy of the GPLv3.
* The source code itself contains the mention:
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
So in the end, it's hard to decide whether it's GPLv2+ or GPLv3+. Maybe
you could contact the author of 'stress' and clarify the situation?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-08 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 2:43 [Buildroot] [PATCH 1/2] stress: fix download url Axel Lin
2013-10-08 2:46 ` [Buildroot] [PATCH 2/2] stress: add license information Axel Lin
2013-10-08 7:15 ` Thomas Petazzoni [this message]
2013-10-08 7:44 ` Axel Lin
2013-10-08 15:36 ` [Buildroot] [PATCH 1/2] stress: fix download url Peter Korsgaard
2013-10-08 15:48 ` Thomas Petazzoni
2013-10-08 20:06 ` Peter Korsgaard
2013-10-08 20:19 ` Peter Korsgaard
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=20131008091546.69d58892@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