All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] nmap: update license
Date: Sat, 6 Oct 2018 15:41:43 +0200	[thread overview]
Message-ID: <20181006154143.44ec552a@windsurf> (raw)
In-Reply-To: <20181004172730.12889-1-fontaine.fabrice@gmail.com>

Hello,

Adding Yann in Cc, licensing question below.

On Thu,  4 Oct 2018 19:27:30 +0200, Fabrice Fontaine wrote:
> nmap is licensed under GPL-2.0 but with exceptions or a commercial
> license (see COPYING, especially the "IMPORTANT NMAP LICENSE TERMS"
> part)
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/nmap/nmap.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/nmap/nmap.mk b/package/nmap/nmap.mk
> index 420aec82d7..6b7502b02b 100644
> --- a/package/nmap/nmap.mk
> +++ b/package/nmap/nmap.mk
> @@ -10,7 +10,7 @@ NMAP_SOURCE = nmap-$(NMAP_VERSION).tar.bz2
>  NMAP_DEPENDENCIES = libpcap
>  NMAP_CONF_OPTS = --without-liblua --without-zenmap \
>  	--with-libdnet=included --with-liblinear=included
> -NMAP_LICENSE = GPL-2.0
> +NMAP_LICENSE = GPL-2.0 with exceptions or commercial

I agree with the GPL-2.0 with exceptions, Debian also calls the license
nmap-GPL-2
(https://metadata.ftp-master.debian.org/changelogs/main/n/nmap/nmap_7.70+dfsg1-3_copyright).

However, I'm not sure about the "or commercial". We used to have that
for Qt, but dropped it, I'm not sure to remember why. Yann ?

>  NMAP_LICENSE_FILES = COPYING
>  
>  # needed by libpcap



-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-06 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 17:27 [Buildroot] [PATCH 1/1] nmap: update license Fabrice Fontaine
2018-10-06 13:41 ` Thomas Petazzoni [this message]
2018-10-06 17:37   ` Yann E. MORIN
2018-10-07 19:40     ` Arnout Vandecappelle
2018-10-08  6:43       ` Thomas Petazzoni
2018-10-08 16:15         ` Arnout Vandecappelle
2018-10-08 19:06           ` Thomas Petazzoni

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=20181006154143.44ec552a@windsurf \
    --to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.