All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] nmap: update license
Date: Mon, 8 Oct 2018 18:15:07 +0200	[thread overview]
Message-ID: <b30432d9-e475-e526-398b-f7ca1b364cbe@mind.be> (raw)
In-Reply-To: <20181008084354.67f19f1e@windsurf>



On 8/10/18 08:43, Thomas Petazzoni wrote:
> Hello,
> 
> On Sun, 7 Oct 2018 21:40:18 +0200, Arnout Vandecappelle wrote:
>> On 6/10/18 19:37, Yann E. MORIN wrote:
>>> So, now, about this specific nmap case... After reviwing the COPYING
>>> file, I would just state:
>>>
>>>     NMAP_LICENSE = GPL-2.0 w/ exception
>>>
>>> But given how specific the nmap project states that they are really
>>> *not* compatible with the GPL-2.0, and as such that exception should
>>> rather be seen as a restriction to the GPL-2.0. So, this is a totally
>>> different license, based on the GPL-2.0, but incompatible with it.
>>>
>>> So, in the end, I would just state:
>>>
>>>     NMAP_LICENSE = nmap license
>>>
>>> and let the user sort the mess on their own, because we can't do much
>>> better... :-/  
>>
>>  I double-checked the nmap license file and I agree with Yann. "nmap license" is
>> the best we can do.
>>
>>  To clarify: the license really is GPL-2.0 with OpenSSL exception. The
>> "additional restriction" is that they add an interpretation of what "derived
>> work" means exactly. It's not really a restriction, but it *does* change the
>> meaning of the license, so calling it GPL-2.0 is not accurate.
> 
> I don't know if that matters, but Debian calls it nmap-GPL-2.

 I think our convention is to use the SPDX term, and if it doesn't exist in SPDX
use "package license".

 I haven't checked though if nmap license exists in SPDX. They do have license
tags for some of the package-specific constructs.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2018-10-08 16:15 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
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 [this message]
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=b30432d9-e475-e526-398b-f7ca1b364cbe@mind.be \
    --to=arnout@mind.be \
    --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.