From: Andreas Enge <andreas@enge.fr>
To: Marius Bakke <marius@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Did nmap just become non-free?
Date: Thu, 15 Oct 2020 10:51:29 +0200 [thread overview]
Message-ID: <20201015085129.GA2559@jurong> (raw)
In-Reply-To: <87r1q0pici.fsf@gnu.org>
Hello,
On Thu, Oct 15, 2020 at 12:12:45AM +0200, Marius Bakke wrote:
> Proprietary software companies wishing to use or incorporate Covered
> Software within their programs must contact Licensor to purchase a
> separate license. Open source developers who wish to incorporate parts
> of Covered Software into free software with conflicting licenses may
> write Licensor to request a waiver of terms.
>
> From <https://svn.nmap.org/nmap/LICENSE>.
>
> So a "proprietary software company" cannot use or incorporate nmap
> within a program, even if that program is free (as in software)?
the formulation is weird, but I am reading this more as "you cannot
incorporate this software into a proprietary one", which more or less
summarises the difference between the GPL and the LGPL.
In guix/licenses.scm, the previous entry for nmap (dating from 2016),
instead of providing a link to https://www.gnu.org/licenses/ , gave one
to https://fedoraproject.org/wiki/Licensing/Nmap , which classifies the
license as free, but incompatible with the GPL.
It would be nice to get feedback from the FSF on the question, indeed;
but I am less pessimistic than you!
Andreas
prev parent reply other threads:[~2020-10-15 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 0:00 Did nmap just become non-free? Marius Bakke
2020-10-14 0:19 ` Brett Gilio
2020-10-14 22:12 ` Marius Bakke
2020-10-14 22:52 ` Brett Gilio
2020-10-15 0:13 ` zimoun
2020-10-15 16:02 ` Brett Gilio
2020-10-15 8:51 ` Andreas Enge [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201015085129.GA2559@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=marius@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).