From: Leo Famulari <leo@famulari.name>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add nmap.
Date: Tue, 15 Mar 2016 04:29:15 -0400 [thread overview]
Message-ID: <20160315082915.GB11456@jasmine> (raw)
In-Reply-To: <877fh4180p.fsf@T420.taylan>
On Tue, Mar 15, 2016 at 09:04:54AM +0100, Taylan Ulrich Bayırlı/Kammer wrote:
> Leo Famulari <leo@famulari.name> writes:
> > + `(#:configure-flags
> > + (list (string-append "--prefix=" (assoc-ref %outputs "out"))
> > + "--without-ncat"
> > + "--without-nmap-update"
> > + "--without-zenmap")))
>
> I think ncat is useful. Does it lead to problems to enable it?
No, I just figured that the netcat package was sufficient. I'll build
ncat in a subsequent version of this patch if desired.
>
> My approach was to install nmap, nse, ncat, and nping to the "out"
> output, and ndiff and zenmap to their own output. I attached my
> half-working patch below. (I wish I had contributed this with some
> parts commented out; at least the nmap/ncat part works fine I believe.)
Thanks, I'll incorporate your patch.
next prev parent reply other threads:[~2016-03-15 8:29 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 [this message]
2016-03-15 8:47 ` Taylan Ulrich Bayırlı/Kammer
2016-03-15 8:24 ` Ricardo Wurmus
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=20160315082915.GB11456@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.com \
/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).