Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] nmap: add option to build/install "ncat"
Date: Tue, 10 Oct 2017 10:12:23 +0200	[thread overview]
Message-ID: <20171010101223.67b1ab6e@windsurf.lan> (raw)
In-Reply-To: <1eb061ff-7182-4ee3-15ab-8f2068db4696@mind.be>

Hello,

On Tue, 10 Oct 2017 00:08:38 +0200, Arnout Vandecappelle wrote:

> 5. BR2_PACKAGE_NMAP builds nothing, two new options BR2_PACKAGE_NMAP_NMAP and
> BR2_PACKAGE_NMAP_NCAT build nmap resp. ncat. To avoid building nothing, you
> could try something like
> 
> config BR2_PACKAGE_NMAP
> 	select BR2_PACKAGE_NMAP_NCAT if !BR2_PACKAGE_NMAP_NMAP
> 
> if BR2_PACKAGE_NMAP
> config BR2_PACKAGE_NMAP_NMAP
> 	default y
> 
> config BR2_PACKAGE_NMAP_NCAT
> endif
> 
> but that might give a circular dependency.

This option has my preference. And it doesn't have a circular
dependency, we use this construct in several places already.

One example:

config BR2_PACKAGE_ANDROID_TOOLS
        bool "android-tools"
        select BR2_PACKAGE_ANDROID_TOOLS_ADBD if \
              !BR2_PACKAGE_ANDROID_TOOLS_FASTBOOT && \
              !BR2_PACKAGE_ANDROID_TOOLS_ADB

if BR2_PACKAGE_ANDROID_TOOLS

config BR2_PACKAGE_ANDROID_TOOLS_FASTBOOT
        bool "fastboot"

config BR2_PACKAGE_ANDROID_TOOLS_ADB
        bool "adb"

config BR2_PACKAGE_ANDROID_TOOLS_ADBD
        bool "adbd"

endif

However, perhaps we should invert the select:

	select BR2_PACKAGE_NMAP_NMAP if !BR2_PACKAGE_NMAP_NCAT

and drop the "default y" in BR2_PACKAGE_NMAP_NMAP. This way, we still
have "nmap" enabled by default, and now allow the option to select ncat.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-10-10  8:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17  7:15 [Buildroot] [PATCH] nc: new virtual package providing "netcat" functionality Carlos Santos
2017-09-17 21:45 ` [Buildroot] [PATCH v2] " Carlos Santos
2017-10-02 14:13   ` [Buildroot] [PATCH v3] " Carlos Santos
2017-10-02 19:18     ` Thomas Petazzoni
2017-10-02 19:44       ` Peter Korsgaard
2017-10-02 20:28         ` Carlos Santos
2017-10-02 20:09       ` Carlos Santos
2017-10-04  9:20         ` Thomas Petazzoni
2017-10-04 12:49           ` [Buildroot] [PATCH] nmap: add option to build/install "ncat" Carlos Santos
2017-10-04 14:08             ` Baruch Siach
2017-10-04 15:43             ` [Buildroot] [PATCH v2] " Carlos Santos
2017-10-06 19:58               ` Arnout Vandecappelle
2017-10-09 16:13                 ` Carlos Santos
2017-10-09 22:08                   ` Arnout Vandecappelle
2017-10-09 22:10                     ` Arnout Vandecappelle
2017-10-09 23:55                       ` Carlos Santos
2017-10-10  0:25                         ` Arnout Vandecappelle
2017-10-10  8:12                     ` Thomas Petazzoni [this message]
2017-10-10 12:42                       ` Yann E. MORIN
2017-10-10 13:32               ` [Buildroot] [PATCH] nmap: add option to build/install ncat Carlos Santos
2017-10-04 12:58           ` [Buildroot] [PATCH v3] nc: new virtual package providing "netcat" functionality Carlos Santos

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=20171010101223.67b1ab6e@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox