From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] inotify-tools: add license information
Date: Wed, 22 Aug 2012 19:45:21 +0200 [thread overview]
Message-ID: <20120822194521.48a4060c@skate> (raw)
In-Reply-To: <1345619321-4644-1-git-send-email-spdawson@gmail.com>
Le Wed, 22 Aug 2012 08:08:40 +0100,
spdawson at gmail.com a ?crit :
> From: Simon Dawson <spdawson@gmail.com>
>
> Signed-off-by: Simon Dawson <spdawson@gmail.com>
> ---
> package/inotify-tools/inotify-tools.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/inotify-tools/inotify-tools.mk b/package/inotify-tools/inotify-tools.mk
> index 52a1701..7c37929 100644
> --- a/package/inotify-tools/inotify-tools.mk
> +++ b/package/inotify-tools/inotify-tools.mk
> @@ -6,3 +6,5 @@
> INOTIFY_TOOLS_VERSION = 3.14
> INOTIFY_TOOLS_SITE = http://github.com/downloads/rvoicilas/inotify-tools/
> $(eval $(autotools-package))
> +INOTIFY_TOOLS_LICENSE = GPLv2+
> +INOTIFY_TOOLS_LICENSE_FILES = COPYING
I've applied this one, but modified the two licensing-related lines to
be above the $(eval $(autotools-package)).
Also, I am not 100% sure how to decide whether this package is GPLv2 or
GPLv2+. The COPYING file contains the text of the GPLv2, but I haven't
found any other place in the source code where the license was
mentioned. So we don't know whether it is GPLv2 only, or "GPLv2 or
later".
I've applied your patch with GPLv2+, and we'll listen to comments from
others if they have a better idea on how to take the proper decision on
this.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-22 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 7:08 [Buildroot] [PATCH] inotify-tools: add license information spdawson at gmail.com
2012-08-22 17:45 ` Thomas Petazzoni [this message]
2012-08-22 19:54 ` Luca Ceresoli
2012-08-22 19:58 ` Thomas Petazzoni
2012-08-22 20:08 ` Luca Ceresoli
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=20120822194521.48a4060c@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