unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add Nmap.
Date: Sun, 23 Nov 2014 21:38:16 +0100	[thread overview]
Message-ID: <87mw7h4pqf.fsf@gnu.org> (raw)
In-Reply-To: <87vbm68743.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Sun, 23 Nov 2014 12:54:36 +0100")

taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:

> 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.

Indeed.

This is normally dealt with by using multiple outputs (info "(guix)
Packages with Multiple Outputs").  An example of that is Git: the Tcl
GUIs are moved to a separate output, and so is git-svn support, such
that the main output does not depend on Tcl, libx11, Subversion, etc.

Would it work here?

Thanks,
Ludo’.

  reply	other threads:[~2014-11-23 20:38 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
2014-11-23 20:38     ` Ludovic Courtès [this message]
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

  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=87mw7h4pqf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).