From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add Nmap.
Date: Sun, 23 Nov 2014 12:54:36 +0100 [thread overview]
Message-ID: <87vbm68743.fsf@taylan.uni.cx> (raw)
In-Reply-To: <20141123090224.GA8260@debian> (Andreas Enge's message of "Sun, 23 Nov 2014 10:02:24 +0100")
Andreas Enge <andreas@enge.fr> writes:
> On Sat, Nov 22, 2014 at 11:05:35PM +0100, "Taylan Ulrich Bayırlı/Kammer" wrote:
>> Many distros separate Zenmap from the Nmap package. Should we do the
>> same? If yes, I'll need some help. This recipe builds it together
>> with the rest of the suite.
>
> Our general policy is to build as intended by upstream with as little
> changes as possible. So unless there is a compelling reason to
> separate the two, I would not do it.
Hm, zenmap would pull in X.Org and all sorts of GUI things, which would
be very annoying for someone who wants nmap on a headless server,
embedded system, or the like.
Well, I didn't need to add any such inputs, and it built zenmap anyway,
but of course it won't run without those. Does that mean I made a
mistake, or is it fine that users have to know what run-time
dependencies to install for certain components of packages to work?
It seems Debian recently split of ndiff as well, after which the nmap
package itself won't depend on Python either, and only has very slim
dependencies. (I *did* have to input python-2 for it to build ndiff and
zenmap...)
This topic seems to tie in well with Gammel Holte's recent post on the
ML regarding how optional run-time dependencies will be handled in Guix.
Maybe we should wait for the outcome of that. Or at least I'll need to
read up on Nix/Guix dependency handling, because I'm confused on what
should and shouldn't be an input.
Taylan
next prev parent reply other threads:[~2014-11-23 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 22:05 [PATCH] gnu: Add Nmap "Taylan Ulrich Bayırlı/Kammer"
2014-11-23 9:02 ` Andreas Enge
2014-11-23 11:54 ` Taylan Ulrich Bayırlı/Kammer [this message]
2014-11-23 20:38 ` Ludovic Courtès
2014-11-23 23:51 ` Taylan Ulrich Bayırlı/Kammer
2014-11-24 14:22 ` Ludovic Courtès
2014-11-24 20:52 ` Taylan Ulrich Bayırlı/Kammer
2014-11-25 21:09 ` Ludovic Courtès
2014-11-25 23:25 ` Taylan Ulrich Bayırlı/Kammer
2014-11-26 2:01 ` Eric Bavier
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=87vbm68743.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.