From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add nmap.
Date: Tue, 15 Mar 2016 09:24:12 +0100 [thread overview]
Message-ID: <87lh5k409f.fsf@mdc-berlin.de> (raw)
In-Reply-To: <fee169f977392e74eed22bbc59331e49694ebcc3.1457995814.git.leo@famulari.name>
Leo Famulari <leo@famulari.name> writes:
> * gnu/packages/admin.scm (nmap): New variable.
> ---
[...]
> + (arguments
> + `(#:configure-flags
> + (list (string-append "--prefix=" (assoc-ref %outputs "out"))
> + "--without-ncat"
> + "--without-nmap-update"
> + "--without-zenmap")))
Could you please explain why these flags are needed?
> + (inputs
> + `(;("liblinear" ,liblinear)
I would just leave this off. You already mention liblinear in a comment
above.
> + ;; The nmap license is based on the GPL 2.0, with several exceptions and
> + ;; modifications. It is incompatible with the GPL 2.0.
> + ;; Nmap's source tarball bundles the source code of many of its
> + ;; dependencies. This package uses nmap's modified version of libdnet and
> + ;; liblinear, which both use a 3-clause BSD license.
> + (license (list license:nmap license:bsd-3))))
We don’t usually explain licenses and compatibility in comments, so I
think it is not necessary to say that the nmap license is based on the
GPL but incompatible.
~~ Ricardo
next prev parent reply other threads:[~2016-03-15 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 22:50 [PATCH 0/2] Add nmap Leo Famulari
2016-03-14 22:50 ` [PATCH 1/2] licenses: Add the nmap license Leo Famulari
2016-03-15 8:21 ` Ricardo Wurmus
2016-03-14 22:50 ` [PATCH 2/2] gnu: Add nmap Leo Famulari
2016-03-15 8:04 ` Taylan Ulrich Bayırlı/Kammer
2016-03-15 8:29 ` Leo Famulari
2016-03-15 8:47 ` Taylan Ulrich Bayırlı/Kammer
2016-03-15 8:24 ` Ricardo Wurmus [this message]
2016-03-15 7:50 ` [PATCH 0/2] " Taylan Ulrich Bayırlı/Kammer
2016-03-15 7:56 ` Leo Famulari
2016-03-15 8:07 ` Taylan Ulrich Bayırlı/Kammer
2016-03-15 8:25 ` Leo Famulari
2016-03-27 21:36 ` Ludovic Courtès
2016-03-27 21:44 ` Leo Famulari
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=87lh5k409f.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).